-
Notifications
You must be signed in to change notification settings - Fork 49
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
Fix flaky e2e test with nondeterministic project list order #5215
base: main
Are you sure you want to change the base?
Conversation
QA Wolf here! As you write new code it's important that your test coverage is keeping up. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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 almost made this same PR to start the process of upgrading yarn. corepack enable
makes this change.
I think creating them in Promise.all was introducing nondeterminism and making tests flaky.
287d8e2
to
ebf8c0a
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5215 +/- ##
=======================================
Coverage 85.95% 85.95%
=======================================
Files 90 90
Lines 32906 32912 +6
=======================================
+ Hits 28285 28291 +6
Misses 4621 4621
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
The test "Opening a project should successfully load the stream" creates two projects. Then it queries the projects, checking both projects were created. However, the projects are returned in a nondeterministic order, which means the test flakes.
I think the nondeterminism is because they're created with a
Promise.all
, so I've instead changed it to create the projects in a specific order.I've also queried the projects in an order-insensitive way.