Skip to main content

Module listing

Module listing 

Source
Expand description

The runners’ own listings: which tests they would run, asked only when the static rule and the JUnit report leave a file undecided. Each runs like a check — sandboxed, scrubbed environment, the check’s deadline.

Structs§

Listed
A listing’s output, or why there is none.

Functions§

go_ids
go test -list: importpath::Name per test, the names grouped by the ok <importpath> line that follows them.
go_names
go test -list .: test names (the ok summary lines left out).
jest_files
jest --listTests: absolute file paths, one per line.
libtest_names
cargo test … -- --list --format terse: name: test lines.
lines
A configured list command: one test id or file path per line.
nextest_ids
cargo nextest list --message-format json: binary-id::test for every test it would run (ignored ones left out).
pytest_ids
pytest --collect-only -q: node ids (path::name).
run
Runs argv in cwd; Err says why it gave no listing.
vitest_files
vitest list --json: the files of the listed tests, relative to root.