-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
feat: [breaking] remove experimentalComponentTesting and require component tests to be run inside of open-ct #15701
Conversation
Thanks for taking the time to open a PR!
|
Test summaryRun details
View run in Cypress Dashboard ➡️ 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 |
@JessicaSachs this is all good now. To confirm you intention was making Also |
Yes @lmiller1990, the exposure of |
…io/cypress into agg23/CTExperimentalDeprecation
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
This PR requires users migrate from the Cypress E2E Runner to the Cypress Component Test Runner. The addition of the
open-ct
andrun-ct
subcommands eliminates the need for a dedicated experimental feature flag (experimentalComponentTesting
).User facing changelog
experimentalComponentTesting
flag has been removed.cypress.json
will throw an error, and component tests may only be run withincypress open-ct
.Additional details
The
file:preprocessor
hook used by the E2E runner to compile specs is incompatible with the newdev-server:start
hook used to compile specs. This change was necessary to cut users over to the new dev server architecture.How has the user experience changed?
open-ct
command.Before: Cypress CT and E2E tests are listed alongside each other
After:
Desktop GUI does not display component tests
Component Test runner displays component tests
PR Tasks
cypress-documentation
?type definitions
?cypress.schema.json
?