-
Notifications
You must be signed in to change notification settings - Fork 111
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
Set up test jail doc & skip current flaky tests #6774
Changes from all commits
5bb2a87
a81ea0b
b87f73f
366eaa1
68e6016
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# Flaky Test Jail | ||
|
||
![flaky test meme](./flaky%20test%20meme.jpeg) | ||
|
||
A list of flaky/misbehaving tests that we are currently skipping in order to keep a green baseline | ||
|
||
## Current Inmates | ||
|
||
#### [Upload Track](./uploadTrack.cy.ts) | ||
|
||
This entire suite is in jail. | ||
|
||
The upload flow seems to generally take too long in CI and results in timeouts and consistent failures. | ||
|
||
#### [Sign Up](./signUp.cy.ts) - [C-3403](https://linear.app/audius/issue/C-3403/get-signup-e2e-green) | ||
|
||
`"should create an account (mobile/desktop)"` are in jail because the new sign up flow is still a WIP and this test + the code needs more work before going green again | ||
|
||
`"can navigate to sign-up from ...xyz (mobile/desktop)"` are in jail due to a bug | ||
with the sign up modal where it just shows the waves background and no content [separate bug ticket](https://linear.app/audius/issue/C-3401/sign-up-sometimes-shows-waves-and-no-content) | ||
|
||
<!-- Template | ||
|
||
#### [Test Name](./link-to-test-file.cy.ts) - [ticket-number](ticket-link) | ||
|
||
Description of which tests and why they're in flaky test jail | ||
|
||
--> | ||
|
||
## Test Jail Process | ||
|
||
- Create an appropriate ticket for addressing the test | ||
- Update this doc with the flaky tests and a description | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't think this is necessary if we have the ticket tbh, or if we do want a description, the comment could have it |
||
- Add a TODO: comment by the test with the ticket number for searchability |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -65,7 +65,8 @@ const completeUpload = () => { | |
}).should('exist') | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I noticed that only one upload test was running due to a |
||
} | ||
|
||
describe('Upload', () => { | ||
// TODO [C-3420]: This suite is in test jail due to upload flows taking too long and timing out | ||
describe.skip('Upload', () => { | ||
beforeEach(() => { | ||
localStorage.setItem('HAS_REQUESTED_BROWSER_PUSH_PERMISSION', 'true') | ||
}) | ||
|
@@ -285,7 +286,9 @@ describe('Upload', () => { | |
completeUpload() | ||
|
||
cy.findByRole('link', { name: /visit track page/i }).click() | ||
cy.findByRole('heading', { name: /pay-gated track/i, level: 1 }).should('exist') | ||
cy.findByRole('heading', { name: /pay-gated track/i, level: 1 }).should( | ||
'exist' | ||
) | ||
cy.findByRole('button', { name: /preview/i }).should('exist') | ||
cy.findByText(/premium track/i).should('exist') | ||
cy.findByText(/users can unlock/i).should('exist') | ||
|
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.
Should we make a client team ticket to fix the upload track suite?