rust/library/test/src, branch master

Rollup merge of #142807 - sourcefrog:failfast, r=dtolnay

2025-09-17T04:56:41+00:00

libtest: expose --fail-fast as an unstable command-line option This exposes the `fail_fast` option added in rust-lang/rust#105153 on the test harness command line, so that workflows that only want to know if any test fails can find out without waiting for everything to run. For example, cargo-mutants just needs to know if any tests fails. It only works with `-Zunstable-options`. Tracking issue: rust-lang/rust#142859

Deprecate RUST_TEST_* env variables

2025-08-11T20:06:32+00:00

This is a documentation-only deprecation for now. Over time, we can - warn and then remove on use of unstable environment variables - warn on use of stable environment variables (no plan to remove due to compatibility) Longer term, we expect test runners, like `cargo test`, to provide the necessary mechanisms for environmental or persistent configuration (e.g. using cargo config which supports `.cargo/config.toml` as well as environment variables). This would include: - `RUST_TEST_THREADS` - `RUST_TEST_NOCAPTURE` - `RUST_TEST_SHUFFLE` (unstable) - `RUST_TEST_SHUFFLE_SEED` (unstable) The primary outcomes for this change are - Reducing the scope of what is expected for custom test harnesses to implement - Reduce the mechanisms that test runners, like `cargo test`, are expected to track when they are being bypassed to protect against negative interactions, e.g. `RUST_TEST_NOCAPTURE=1` when json output is being read.

Add new `test::print_merged_doctests_times` used by rustdoc to display more detailed time information and add new `OutputFormatter::write_merged_doctests_times` method to handle it

2025-08-04T14:06:56+00:00

Make `libtest::ERROR_EXIT_CODE` const public to not redefine it in rustdoc

2025-07-31T08:44:50+00:00

Make fail-fast unstable

2025-06-20T20:27:53+00:00

libtest: expose --fail-fast

2025-06-20T20:22:14+00:00

Add new `test_main_with_exit_callback` public function in `libtest` to allow a callback to be called before exiting

2025-05-06T16:17:48+00:00

Remove backticks from `ShouldPanic::YesWithMessage`'s `TrFailedMsg`

2025-04-28T19:40:29+00:00

fix(test): Expose '--no-capture', deprecating '--nocapture'

2025-04-17T18:30:59+00:00

This improves consistency with commonly expected CLI conventions, avoiding a common stutter people make when running tests (trying what they expect and then having to check the docs to then user whats accepted). An alternative could have been to take a value, like `--capture ` (e.g. `pytest` does this). Overall, we're shifting focus for features to custom test harnesses (see #134283). Most of `pytest`s modes will likely be irrelevant in that situation. As for the rest, its too early to tell which, if any, may be relevant, so we're sticking with this small, quality of life improvement. By deprecating `--nocapture`, we intend that custom test harnesses do not need to support it for reasons outside of their own compatibility requirements, much like the deprecation in #134283 I'm punting for now on the naming of `RUST_TEST_NOCAPTURE`. I feel like T-testing-devex should do a wider look at environment variables role in lib`test` before evaluating whether to - Deprecate it in favor of the user passing CLI flags or the test runner providing its own config - Deprecate in favor of `RUST_TEST_NO_CAPTURE` - Deprecate in favor of `RUST_TEST_CAPTURE` Other CLI flags were evaluated for casing consistency: - `--logfile` has the same problem but was deprecated in #134283 Fixes #133073

refactor(test): Decouple parsing from help generation

2025-04-17T18:30:59+00:00

This will help with hiding some options in `--help`