The `beskid dev build test` CLI

Informative guide. This Book page explains Beskid but does not define the standard. For normative requirements, use the Beskid Standard.

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

beskid dev build test path/to/Harness.bd
beskid dev build test --project path/to/Project.proj

See beskid dev build test reference for full flags (--target, --workspace-member, lockfile modes).

Filtering

beskid dev build test Src/Harness.bd --include-tag fast --group analysis
beskid dev build test Src/Harness.bd --exclude-tag slow

• --include-tag — run only tests whose meta.tags contain a tag (repeatable).
• --exclude-tag — drop tests with matching tags.
• --group — prefix match on meta.group.

Machine-readable output

beskid dev build test Src/Harness.bd --json

Buckets: 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

beskid dev build test shares project resolution with beskid dev build compile and beskid dev syntax analyze: same graph, same lockfile story. If resolution fails, no tests run—by design.

Normative tooling

• Build / analyze / run contract
• Testing reference

Next

Arrange, act, assert