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
fix: test config overrides leak for .only execution #18961
Conversation
Thanks for taking the time to open a PR!
|
Test summaryRun details
View run in Cypress Dashboard ➡️ Flakiness
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 |
systemTests.it(`correctly applies overrides when valid configuration for describe.only`, { | ||
spec: 'testConfigOverrides-describe-only-valid.js', | ||
snapshot: true, | ||
expectedExitCode: 0, | ||
config: { | ||
video: false, | ||
}, | ||
}) | ||
|
||
systemTests.it(`correctly applies overrides when valid configuration for it.only`, { | ||
spec: 'testConfigOverrides-it-only-valid.js', | ||
snapshot: true, | ||
expectedExitCode: 0, | ||
config: { | ||
video: false, | ||
}, | ||
}) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these don't need to be system tests, they can be regular driver Cypress tests instead, right? Since we run one test file at a time in cypress run
, it should work the same. packages/driver/cypress/integration/e2e
would be a good place.
Avoid adding system tests if possible since they're a lot heavier, resource-wise. And since we're just running the test and the snapshot doesn't have any additional info in it, it should be fine to make these regular Cypress tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmmm good point. Updated: 96e4e80
(#18961)
* develop: test: node_modules installs for system-tests, other improvements (#18574) chore(deps): update dependency semantic-release to v17.2.3 [security] (#19022) chore: remove flaky ci jobs for main builds (#19071) chore(contributing): clarify PULL_REQUEST_TEMPLATE (#19068) fix: the shadow root container element is ignored when clicking an element in it. (#18908) 'Fix' flaky redirect test (#19042) release 9.1.0 [skip ci] fix: Allow 'this' to be used in overridden commands (#18899) fix(react): link to rerender example (#19020) chore(deps): update dependency aws-sdk to v2.814.0 [security] (#18948) fix: test config overrides leak for .only execution (#18961) feat: Set CYPRESS=true as env var in child processes where Cypress runs user code in Node (#18981) fix: Restore broken gif (#18987) chore: release @cypress/vite-dev-server-v2.2.1
* 10.0-release: feat(graphql): ability to update/query for appData (#19082) fix system test fix failing tests due to merge resolve conflicts test: node_modules installs for system-tests, other improvements (#18574) update yarn.lock chore(deps): update dependency semantic-release to v17.2.3 [security] (#19022) chore: remove flaky ci jobs for main builds (#19071) chore(contributing): clarify PULL_REQUEST_TEMPLATE (#19068) fix: the shadow root container element is ignored when clicking an element in it. (#18908) 'Fix' flaky redirect test (#19042) release 9.1.0 [skip ci] fix: Allow 'this' to be used in overridden commands (#18899) fix(react): link to rerender example (#19020) chore(deps): update dependency aws-sdk to v2.814.0 [security] (#18948) fix: test config overrides leak for .only execution (#18961) feat: Set CYPRESS=true as env var in child processes where Cypress runs user code in Node (#18981) fix: Restore broken gif (#18987) chore: release @cypress/vite-dev-server-v2.2.1
Recent change to add configuration validation required updates to include the invocation details to throw an invalidation configuration error with the correct line number of where the configuration was passed in for suite/test configuration. These changed did not account for single suite/test execution which was normalized more than once.
How has the user experience changed?
The configuration appears to have been applying correctly, so should be minimal to no impact on consumers.
PR Tasks