-
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
hooks can rerun on unrelated tests after top navigation #17705
Labels
v8.2.0 🐛
Issue present since 8.2.0
Comments
kuceb
changed the title
hooks can rerun on unrelated tests after top navigation due to cy.visit
hooks can rerun on unrelated tests after top navigation
Aug 11, 2021
6 tasks
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
stage: work in progress
and removed
stage: work in progress
stage: needs review
The PR code is done & tested, needs review
labels
Aug 25, 2021
Please be sure to also check the case of visiting multiple superdomains, as described in #17940 |
cypress-bot
bot
added
stage: needs review
The PR code is done & tested, needs review
and removed
stage: work in progress
labels
Sep 1, 2021
cypress-bot
bot
added
stage: pending release
and removed
stage: needs review
The PR code is done & tested, needs review
labels
Sep 9, 2021
The code for this is done in cypress-io/cypress#17884, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Current behavior
example: session_spec running hooks multiple times after navigation: https://app.circleci.com/pipelines/github/cypress-io/cypress/22975/workflows/4a639267-6eda-4e78-84b6-5c1f3426f04e/jobs/845803/parallel-runs/7
This occurs when a global before/after hook is present
Desired behavior
before/after hooks should only be run once and on correct suite
Test code to reproduce
n/a
Cypress Version
8.2.0
Other
No response
The text was updated successfully, but these errors were encountered: