-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
allow to disable cache when running tests in browser #1315
Comments
This is true. We intend to do this as part of the Lifecycle Events Epic. #686 We also just closed an issue today related to this - we are now clearing the cache once when the browser is launched - but not in between tests. We'll do that as per the Lifecycle events. As for testing this today - there's not really any reason to do a browser test to do this as per your repo - you can just use |
Thanks feel free to close if you like, I worked around the issue in my case. |
Was just reminded that |
Current behavior:
When testing 301 redirect behavior that differs based on passed headers the tests will fail after first run because a browser caches 301 redirects
Desired behavior:
It would be nice to test each run in isolation by disabling the browser cache
How to reproduce:
https://github.com/gr2m/cypress-test-tiny/tree/cypress-1315
Test code:
See link to repository above
Additional Info (images, stack traces, etc)
Browser redirects based on cached 301 redirect
Which makes test fail
Test pass when "disable cache" flag is checked (in the network tab of developer tools)
The text was updated successfully, but these errors were encountered: