cypress
cypress copied to clipboard
fix: clear session state when changing specs in open mode
While working on persisting sessions between specs, I noticed we were incorrectly persisting sessions in open mode when navigating between specs from the in-line spec list.
User facing changelog
Corrected an issue where session state was not being reset when changing between specs in open mode. Fixed by .
How has the user experience changed?
Users switching between tests int he spec-finder should have a clean slate like in run mode.
PR Tasks
- [x] Have tests been added/updated?
- [x] Has the original issue (or this PR, if no issue exists) been tagged with a release in ZenHub? (user-facing changes only)
- [n/a] Has a PR for user-facing changes been opened in
cypress-documentation
? - [n/a] Have API changes been updated in the
type definitions
?
Thanks for taking the time to open a PR!
- Create a Draft Pull Request if your PR is not ready for review. Mark the PR as Ready for Review when you're ready for a Cypress team member to review the PR.
- Become familiar with the Code Review Checklist for guidelines on coding standards and what needs to be done before a PR can be merged.
Test summary
Run details
Project | cypress |
Status | Passed |
Commit | bc927c152d |
Started | Aug 12, 2022 5:04 PM |
Ended | Aug 12, 2022 5:24 PM |
Duration | 20:05 💡 |
OS | Linux Debian - 11.3 |
Browser | Multiple |
View run in Cypress Dashboard ➡️
Flakiness
![]() |
e2e/origin/commands/actions.cy.ts ![]() |
1 ![]() |
|
---|---|---|---|
1 | cy.origin actions > #consoleProps > .submit() | ||
![]() |
cypress/proxy-logging.cy.ts ![]() |
2 ![]() |
|
1 | Proxy Logging > request logging > xhr log has response body/status code when xhr response is logged second | ||
2 | Proxy Logging > request logging > xhr log has response body/status code when xhr response is logged second | ||
![]() |
e2e/origin/commands/assertions.cy.ts ![]() |
1 ![]() |
|
1 | cy.origin assertions > #consoleProps > .should() and .and() |
This comment has been generated by cypress-bot as a result of this project's GitHub integration settings. You can manage this integration in this project's settings in the Cypress Dashboard
Released in 10.5.0
.
This comment thread has been locked. If you are still experiencing this issue after upgrading to Cypress v10.5.0, please open a new issue.