-
Notifications
You must be signed in to change notification settings - Fork 3.3k
chore: add ui states tests #31768
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
chore: add ui states tests #31768
Conversation
cypress
|
Project |
cypress
|
Branch Review |
alejandro/chore/add-ui-states-tests
|
Run status |
|
Run duration | 16m 33s |
Commit |
|
Committer | Alejandro Estrada |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
2
|
|
133
|
|
0
|
|
5559
|
View all changes introduced in this branch ↗︎ |
…d improving visibility checks
…, hooks, nested tests, page events, and status codes. Update existing tests to improve structure and visibility checks.
…ptions, enhancing visibility checks and structure. Updated test descriptions for clarity and added new test cases for better coverage.
…nd adding new tests for enhanced coverage. Introduced a new file for commands to display in UI, and updated existing tests to improve structure and naming conventions.
…prove maintainability. This cleanup focuses on consolidating test cases and enhancing overall structure.
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.
Only thing I would really like to see different is some more specific naming around the things we are testing. Otherwise, I really like the general idea of having some better snapshots in percy to make sure there aren't visual regressions with the UI!
}) | ||
|
||
it('hooks', () => { | ||
runSpec({ |
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.
instead of runSpec
, can we leverage loadSpec
with the correct num of 'pass/
failed assertions to avoid the
cypress:in:cypress:run:complete` event? That method should wait for the test to finnish
system-tests/project-fixtures/runner-specs/cypress/e2e/runner/ui-states/commands.cy.js
Outdated
Show resolved
Hide resolved
…e with parts 4, 5, and 6. Updated existing test descriptions for clarity and improved structure in the Cypress test suite.
Additional details
Add a set of UI states that can be useful for snapshots when there're UI changes, ensuring the behavior persist
Steps to test
How has the user experience changed?
PR Tasks
cypress-documentation
?type definitions
?