beskid test

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

Run Beskid test items declared with test Name { ... }. This command is available as beskid test.

Usage

beskid test [INPUT] [--project <path>] [--target <name>] [--workspace-member <name>]

Options

• --include-tag <tag> (repeatable): run only tests containing any included tag
• --exclude-tag <tag> (repeatable): exclude tests containing any excluded tag
• --group <prefix>: run only tests whose meta.group starts with <prefix>
• --json: print JSON summary and per-test records
• --plain: disable animated progress and graph output
• --all-targets: run all Test targets in one process with one prepared workspace
• --frozen / --locked: project resolution lockfile controls (same behavior as other project-aware commands)

Behavior

• Tests are discovered from parsed source (test items at top-level and inline modules).
• The current test engine executes prepared test entrypoints with JIT. This is separate from the AOT beskid run path.
• skip.condition = true marks a test as skipped and bypasses execution.
• Exit code is non-zero when any test fails.

Example

beskid test Src/Harness.bd --include-tag fast --group analysis