c1a31d8103
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. |
||
|---|---|---|
| .. | ||
| formatters | ||
| helpers | ||
| stats | ||
| term | ||
| bench.rs | ||
| cli.rs | ||
| console.rs | ||
| event.rs | ||
| lib.rs | ||
| options.rs | ||
| stats.rs | ||
| term.rs | ||
| test_result.rs | ||
| tests.rs | ||
| time.rs | ||
| types.rs | ||