You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using Capybara for integration testing. My observers work fine in my app and in my regular tests, but Capybara feature tests do not trigger any observers no matter what I try. Has anyone dealt with this or is this a known or intentional behavior?
I'm using the latest version of RSpec, Capybara (github masters) and Rails 5.0.0beta3.
The text was updated successfully, but these errors were encountered:
Ended up completely refactoring my entire app away from observers, days of work, just because I could not find a way around this. In some cases it actually made my code better because I was able to abstract it even further into concerns, but in other cases I still believe that observers make for better software engineering than model callbacks. I was sad to have to do it for those cases.
It seems that once observers were dropped from the core of Rails that the community has pretty much abandoned them - so I was forced to do so as well.
i'm experiencing this as well, since upgrading from rails 4.2 to 5.1. however, for me it's only intermittent. i'm updating the model in the test suite's setup; sometimes the observer fires and sometimes it doesn't (consistent amongst a single run of the suite though).
I'm using Capybara for integration testing. My observers work fine in my app and in my regular tests, but Capybara feature tests do not trigger any observers no matter what I try. Has anyone dealt with this or is this a known or intentional behavior?
I'm using the latest version of RSpec, Capybara (github masters) and Rails 5.0.0beta3.
The text was updated successfully, but these errors were encountered: