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
Capybara is for simulating user experience, since a user never sees a 301 I wouldnt expect to test that with Capybara. You'll get more complete answers by positing to the mailing list mentioned in the README, but if you really need to verify a 301 is sent (instead of a 302 or something) rather than just the result of the url changing then you probably just need a standard controller spec and dont involve capybara at all - https://www.relishapp.com/rspec/rspec-rails/docs/controller-specs
Is this possibly a capybara issue?
http://stackoverflow.com/questions/18030507/how-to-verify-301-status-code-using-capybara-webkit
Capybara-Webkit (and poltergeist) works fine to confirm a status code of 200 or 404, but when I do a redirect (301), I get back a status code of 200.
So this always fails
I can verify that the right page is shown with the redirect:
Any advice? Skip the check on the 301 status?
The text was updated successfully, but these errors were encountered: