devise: undefined method `rails5?' for Devise::Test:Module in 4.4.2
Environment
- Ruby 2.3.5
- Rails 5.1.5
- Devise 4.4.2
Current behavior
Controller specs where the user is not authenticated fail with this exception:
undefined method `rails5?' for Devise::Test:Module in 4.4.2
An example stack trace is:
NoMethodError:
undefined method `rails5?' for Devise::Test:Module
# /Users/moncefbelyamani/.gem/ruby/2.3.5/gems/devise-4.4.2/lib/devise/test/controller_helpers.rb:142:in `_process_unauthenticated'
# /Users/moncefbelyamani/.gem/ruby/2.3.5/gems/devise-4.4.2/lib/devise/test/controller_helpers.rb:118:in `_catch_warden'
# /Users/moncefbelyamani/.gem/ruby/2.3.5/gems/devise-4.4.2/lib/devise/test/controller_helpers.rb:35:in `process'
# /Users/moncefbelyamani/.gem/ruby/2.3.5/gems/actionpack-5.1.5/lib/action_controller/test_case.rb:392:in `get'
# /Users/moncefbelyamani/.gem/ruby/2.3.5/gems/rails-controller-testing-1.0.2/lib/rails/controller/testing/integration.rb:12:in `block (2 levels) in <module:Integration>'
# ./spec/controllers/application_controller_spec.rb:103:in `block (4 levels) in <top (required)>'
Expected behavior
Tests that used to pass with Devise 4.4.1 continue to pass when upgrading Devise to 4.4.2
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 14
- Comments: 15 (6 by maintainers)
Commits related to this issue
- Updated bundle. Devise test is failing, but it's a known bug: https://github.com/plataformatec/devise/issues/4808 — committed to sighmon/NI by sighmon 6 years ago
@rikkipitt I hope to release it today. There’s another fix I want to include in this patch, but I think we can finish today.
@elrayle sorry for taking so long to reply. It turns out I couldn’t get the other fix ready until today. But version
4.4.3is now released.Thanks everyone for your patience.
@tegon Is release happening today? We are considering pinning to keep our work moving forward, but if it is going to be released any minute… we’ll wait.
38 minutes after this was closed, I just had this issue too! When is the next proposed release to include this fix?
Cheers.