nextest is a tool for running Rust tests, as a replacement for
You can use nextest to run your tests with cargo-mutants, instead of
cargo test, by either passing the
--test-tool=nextest option, or setting
test_tool = "nextest" in
In the context of cargo-mutants the most important difference between cargo-test and nextest is that nextest runs each test in a separate process, and it can run tests from multiple test targets in parallel. (Nextest also has some nice UI improvements and other features, but they're not relevant here.)
This means that nextest can stop faster if a single test fails, whereas cargo test will continue running all the tests within the test binary.
This is beneficial for cargo-mutants, because it only needs to know whether at least one test caught the mutation, and so exiting as soon as there's a failure is better.
However, running each test individually also means there is more per-test startup cost, and so on some trees nextest may be slower.
In general, nextest will do relatively poorly on trees that have tests that are individually very fast, or on trees that establish shared or cached state across tests.
There are at least two reasons why you might want to use nextest:
Some Rust source trees only support testing under nextest, and their tests fail under
cargo test: in that case, you have to use this option! In particular, nextest's behavior of running each test in a separate process gives better isolation between tests.
Some trees might be faster under nextest than under
cargo test, because they have a lot of tests that fail quickly, and the startup time is a small fraction of the time for the average test. This may or may not be true for your tree, so you can try it and see. Some trees, including cargo-mutants itself, are slower under nextest.
Caution: nextest currently does not run doctests, so behaviors that are only caught by doctests will show as missed when using nextest. (cargo-mutants could separately run the doctests, but currently does not.)