Skip to content

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

Merged
merged 14 commits into from
May 23, 2025
Merged

Conversation

estrada9166
Copy link
Member

  • Closes

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

Copy link

cypress bot commented May 21, 2025

cypress    Run #62646

Run Properties:  status check passed Passed #62646  •  git commit d3ee106609: Merge branch 'develop' into alejandro/chore/add-ui-states-tests
Project cypress
Branch Review alejandro/chore/add-ui-states-tests
Run status status check passed Passed #62646
Run duration 16m 33s
Commit git commit d3ee106609: Merge branch 'develop' into alejandro/chore/add-ui-states-tests
Committer Alejandro Estrada
View all properties for this run ↗︎

Test results
Tests that failed  Failures 0
Tests that were flaky  Flaky 2
Tests that did not run due to a developer annotating a test with .skip  Pending 133
Tests that did not run due to a failure in a mocha hook  Skipped 0
Tests that passed  Passing 5559
View all changes introduced in this branch ↗︎

…, 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.
Copy link
Contributor

@AtofStryker AtofStryker left a 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({
Copy link
Contributor

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 thecypress:in:cypress:run:complete` event? That method should wait for the test to finnish

…e with parts 4, 5, and 6. Updated existing test descriptions for clarity and improved structure in the Cypress test suite.
@estrada9166 estrada9166 requested a review from AtofStryker May 23, 2025 16:53
@AtofStryker AtofStryker merged commit b5e2f7a into develop May 23, 2025
89 of 91 checks passed
@AtofStryker AtofStryker deleted the alejandro/chore/add-ui-states-tests branch May 23, 2025 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants