-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Open
Labels
A-libtestArea: `#[test]` / the `test` libraryArea: `#[test]` / the `test` libraryC-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-dev-toolsRelevant to the dev-tools subteam, which will review and decide on the PR/issue.Relevant to the dev-tools subteam, which will review and decide on the PR/issue.
Description
The ability to repeat tests in-process is useful when attempting to reproduce flaky test failures. Go's testing package has the -count
flag (https://golang.org/cmd/go/#hdr-Testing_flags), googletest has --gtest_repeat
(https://github.com/google/googletest/blob/master/googletest/docs/advanced.md#repeating-the-tests), but rust doesn't seem to have anything.
In a limited test, I ran a test binary 100 times with a filter that excluded all test cases, and that took over 15 seconds. It'd be nice to avoid that overhead.
cc @tmandry
cramertj, benbrittain, ehuss, ctiller, brunowonka and 4 more
Metadata
Metadata
Assignees
Labels
A-libtestArea: `#[test]` / the `test` libraryArea: `#[test]` / the `test` libraryC-feature-requestCategory: A feature request, i.e: not implemented / a PR.Category: A feature request, i.e: not implemented / a PR.T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.T-dev-toolsRelevant to the dev-tools subteam, which will review and decide on the PR/issue.Relevant to the dev-tools subteam, which will review and decide on the PR/issue.
Type
Projects
Status
No status