- Parallel, possibility to run tests in parallel.
- Fail fast, stop testing as soon as first test failed.
- Last failed, possibility to run tests that were failed in the last run.
- Impact analysis, possibility to choose only those tests that covers new changes.
- Grouping, possibility to group test by attributes.
- Shuffle, possibility to run tests in random order.
|Tool||Language||Parallel||Fail Fast||Last Failed||Impact Analysis||Grouping||Shuffle|
||Rust||Yes||Yes (by default)||No4|
- The go test command now caches test results: if the test executable and command line match a previous run and the files and environment variables consulted by that run have not changed either, go test will print the previous test output, replacing the elapsed time with the string “(cached).” Test caching applies only to successful test results; only to go test commands with an explicit list of packages; and only to command lines using a subset of the -cpu, -list, -parallel, -run, -short, and -v test flags. The idiomatic way to bypass test caching is to use -count=1. (Go 1.10+)
- Crystalball, whattorun
- nose-knows is a nose plugin for figuring out which unit tests you should run after modifying code. It works by tracing your code while you run unit tests, and creating an output file that can be used later.
- pytest-knows, pytest-incremental, pytest-picked, pytest-cache, pytest-testmon, smother, python-tia, pytest-smartcollect and more
- Since PHPUnit v7.3
- fastest, paratest
--rerun-failedoption was added to CTest in CMake 3.0
- The new go test
-failfastflag disables running additional tests after any test fails. Note that tests running in parallel with the failing test are allowed to complete. (Go 1.10+)
- Allow parallel execution of test functions that call t.Parallel. The value of this flag is the maximum number of tests to run simultaneously; by default, it is set to the value of GOMAXPROCS. Note that -parallel only applies within a single test binary. The ‘go test’ command may run tests for different packages in parallel as well, according to the setting of the -p flag.
- The -short mode for go test allows us to mark any long-running tests to be skipped in this mode. go test and the testing package support this via the t.Skip(), the testing.Short() functions and the -short flag.
- pytest-random-order, pytest-randomly