feat(test-runner): add repeat config in test#41287
Open
vctqs1 wants to merge 5 commits into
Open
Conversation
Author
|
@microsoft-github-policy-service agree |
vctqs1
commented
Jun 13, 2026
| // drive letter for a URL scheme ("Received protocol 'c:'"). | ||
| // The `import` condition is present only for ESM resolution, so use it to pick the form. | ||
| specifier = context.conditions?.includes('import') ? url.pathToFileURL(resolved).toString() : resolved; | ||
| specifier = context.conditions?.includes?.('import') ? url.pathToFileURL(resolved).toString() : resolved; |
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
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.

Motivation
Playwright currently provides:
--retries=Nto rerun failed tests--repeat-each=Nto rerun every test multiple timesHowever, there is no built-in mechanism to repeatedly execute only a subset of tests.
This becomes useful when investigating flaky tests or validating the stability of a newly added test. In these scenarios, running the entire suite repeatedly can be expensive and time-consuming, while retries only execute after failures occur.
Example
The test would execute 20 consecutive times regardless of pass/fail status.
Use Cases
Why existing features are insufficient
--retries--repeat-eachThis proposal provides a targeted alternative focused on individual tests.