feat(test-utils): Add a flaky test marker #497
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
grypez
force-pushed
the
grypez/mark-flaky-tests
branch
from
512731d to
7faffdc
Compare
Contributor
Author
|
overkill |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds a
flakyfunction totest-utilswhich, when supplied to vitest'sitoptions, causes the test to automatically retry.Note to Reviewers
Properly applied, this marker function should make it easy to identify flaky tests at rest. When no tests are known to be flaky, we could remove the line
export { flaky } from './flaky.ts'from test-utils'index.ts.Are there other known flaky tests?