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::Nameper test, the names grouped by theok <importpath>line that follows them.- go_
names go test -list .: test names (theoksummary lines left out).- jest_
files jest --listTests: absolute file paths, one per line.- libtest_
names cargo test … -- --list --format terse:name: testlines.- lines
- A configured
listcommand: one test id or file path per line. - nextest_
ids cargo nextest list --message-format json:binary-id::testfor every test it would run (ignored ones left out).- pytest_
ids pytest --collect-only -q: node ids (path::name).- run
- Runs
argvincwd;Errsays why it gave no listing. - vitest_
files vitest list --json: the files of the listed tests, relative toroot.