08.2 The beskid test CLI
Discover, filter, and summarize Beskid test items from the command line.
The beskid test CLI
The CLI does not care about your feelings. It cares about discovery, skip predicates, and a non-zero exit code when something fails.
Basic run
Section titled “Basic run”beskid test path/to/Harness.bdbeskid test --project path/to/Project.projSee beskid test reference for full flags (--target, --workspace-member, lockfile modes).
Filtering
Section titled “Filtering”beskid test Src/Harness.bd --include-tag fast --group analysisbeskid test Src/Harness.bd --exclude-tag slow--include-tag— run only tests whosemeta.tagscontain a tag (repeatable).--exclude-tag— drop tests with matching tags.--group— prefix match onmeta.group.
Machine-readable output
Section titled “Machine-readable output”beskid test Src/Harness.bd --jsonBuckets: passed, failed, skipped, filtered_out. CI parsers should treat skipped separately from failed—unless your team uses skip as passive-aggressive deletion, in which case fix the culture, not the JSON.
Wiring to analysis
Section titled “Wiring to analysis”beskid test shares project resolution with build and analyze: same graph, same lockfile story. If resolution fails, no tests run—by design.