-
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
break: addSelector, and rework of cy.should() #23631
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…removal (and be more complete)
…otting when retrying selectors
Thanks for taking the time to open a PR!
|
Test summaryRun details
View run in Cypress Dashboard ➡️ FailuresFlakiness
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 |
After discussing with the team, came to the conclusion that many of these changes are unnecessary. Closing this in favor of a clean branch / PR incoming shortly. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
User facing changelog
This PR targets a newly created feature branch rather than develop, so these 'user facing changes' are incomplete and will be added to by future PRs before ending up in the changelog.
This PR contains three major changes:
Cypress.Commands.addSelector()
, in packages/driver/src/cypress/commands.ts and packages/driver/src/cypress/command_queue.ts.should()
from a special-case utility command that "folds into" earlier commands viaverifyUpcomingAssertios
to its own, full-fledged independent command, in packages/driver/src/cy/commands/asserting.ts..get()
to be the first selector, and moving Aliases to use concept of "subject chains" rather than re-running commands via the command queue, in packages/driver/src/cy/commands/querying/querying.ts and packages/driver/src/cy/commands/aliasing.ts.Additional details
Many tests are currently failing, and others have been commented out. Red builds are expected at the moment.
The intention is to have all tests passing and no tests skipped by the time this work is ready to merge into develop - but getting everything passing again will require further code churn, and I wanted to limit the scope of this already large PR as much as possible.
Fixing these commented out and failing tests will be the work of future PRs against the same branch.
Steps to test
For now please focus on the tests and functionality in /packages/driver.
All commands should be functional, but .should() will fail on many of them at the moment. .get() and .root() should be completely working, but, eg. .contains(), .attr(), .location() will not retry correctly.
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?