Skip to content
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

FLAKY TEST: court-issued-documents.cy.ts #4015

Open
3 tasks
Absolutestunna opened this issue Sep 28, 2023 · 2 comments
Open
3 tasks

FLAKY TEST: court-issued-documents.cy.ts #4015

Absolutestunna opened this issue Sep 28, 2023 · 2 comments

Comments

@Absolutestunna
Copy link
Contributor

Absolutestunna commented Sep 28, 2023

Path to Test File

cypress/cypress-smoketests/integration/court-issued-documents.cy.ts

Readout of the failure

Screenshot 2023-09-28 at 9 45 41 AM

Github Actions CI
Screenshot 2023-10-17 at 5 24 10 PM

Printout after refactor in 4177
Screenshot 2023-10-24 at 12 19 40 PM

Workflows of Failure(s)

CircleCI Smoketest failure

GA Smoketest_Local, 4177

What were you working on?

4001
4100
4122

Notes

Definition of Done (Updated 4-14-21)

Engineering

  • Documentation has been added to this card with any helpful information relating to the test failures.
  • Test has been fixed or removed.
  • Test has been reattempted 5 times without fail.
@Absolutestunna Absolutestunna changed the title FLAKY TEST: CYPRESS: court-issued-documents.cy.ts FLAKY TEST: court-issued-documents.cy.ts Sep 28, 2023
@Absolutestunna Absolutestunna changed the title FLAKY TEST: court-issued-documents.cy.ts FLAKY TEST: court-issued-documents.cy.ts Sep 28, 2023
@rachelschneiderman
Copy link
Contributor

image

@Absolutestunna
Copy link
Contributor Author

Absolutestunna commented Oct 25, 2023

Solution ideas/implementation for resolution

  1. Separate flows for e-filed petitions and paper petitions. Improves legibility and predictability of the tests.
  2. Add data-cy attributes to confirmation icons so we can specifically verify the status of the upload

Please review the PR for more information.

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

No branches or pull requests

2 participants