Skip to content

docs: note newly-ignored failure mode in new_test.rs module doc #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cargo-affected-bot wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: note newly-ignored failure mode in new_test.rs module doc #65

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f01354e
docs: note newly-ignored failure mode in new_test.rs module doc
cargo-affected-bot Jul 21, 2026
063c289
Merge remote-tracking branch 'origin/main' into docs/new-test-module-…
cargo-affected-bot Jul 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 8 additions & 6 deletions tests/functional/new_test.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,14 @@
//! data, so it can't be range-matched. The selection layer is supposed to
//! list it via nextest and tag it `(new)` in the verbose output.
//!
//! Two failure modes are guarded here. A perpetually-`#[ignore]`d test is
//! always listed but never collected, so it must not read as "new" forever.
//! And the listing must build with the same cargo features as the run, or a
//! feature-gated new test is invisible to detection — checked for `run` and
//! for `status`, which has to reach the same answer to be worth anything as a
//! dry run.
//! Several failure modes are guarded here. A perpetually-`#[ignore]`d test is
//! always listed but never collected, so it must not read as "new" forever. A
//! test that becomes `#[ignore]`d after collection keeps its coverage rows, so
//! it must be dropped from the `affected` selection too — a separate path from
//! new-test detection. And the listing must build with the same cargo features
//! as the run, or a feature-gated new test is invisible to detection — checked
//! for `run` and for `status`, which has to reach the same answer to be worth
//! anything as a dry run.

use std::path::Path;

Expand Down
Loading