-
Notifications
You must be signed in to change notification settings - Fork 178
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
E2E Tests: retry flaky tests #7758
Conversation
Size Change: 0 B Total Size: 2.11 MB ℹ️ View Unchanged
|
Codecov Report
@@ Coverage Diff @@
## main #7758 +/- ##
==========================================
+ Coverage 82.56% 84.37% +1.80%
==========================================
Files 1155 1158 +3
Lines 17428 17449 +21
==========================================
+ Hits 14390 14722 +332
+ Misses 3038 2727 -311
Flags with carried forward coverage won't be shown. Click here to find out more.
|
@@ -112,6 +112,11 @@ const pageEvents = []; | |||
// The Jest timeout is increased because these tests are a bit slow | |||
jest.setTimeout(PUPPETEER_TIMEOUT || 100000); | |||
|
|||
// Retry flaky tests at most 2 times in CI (off by 1). |
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.
I don't think this is correct though. I believe retryTimes(3)
means it will at most run the test 4 times, 1 normal run, then 3 retries.
Context
Summary
Prior art: WordPress/gutenberg#31682
Requires jest-circus test runner, which is the default since Jest 27.
Retry 3 means that test is run 3 times, normally and 2 other times.
Relevant Technical Choices
To-do
User-facing changes
Testing Instructions
QA
This PR can be tested by following these steps:
UAT
This PR can be tested by following these steps:
Reviews
Does this PR have a security-related impact?
Does this PR change what data or activity we track or use?
Does this PR have a legal-related impact?
Checklist
Type: XYZ
label to the PRFixes #7549