bldr test
Build a workspace (or a member) and report its test results: every `ctx.addTest(name, …)` target is built, then the daemon's aggregated per-case verdict is printed. Exits non-zero if any case failed
bldr test
Build a workspace (or a member) and report its test results: every ctx.addTest(name, …) target is built, then the daemon's aggregated per-case verdict is printed. Exits non-zero if any case failed
bldr [BLDR FLAGS] test [TEST FLAGS] [FILTER]...<FILTER>
What to test: target filters, additive (see bldr build). Omitted → the workspace's default filters
May be given more than once.
-W, --workspace <PATH>
Target workspace directory. Defaults to the one discovered by walking up from the current directory
-a, --all
Show every case (passed and skipped too), not just failures
Defaults to false.
--tree
Show the build's task tree while it runs.
Off by default, because the answer bldr test exists to give is the verdict, and the tree is thousands of lines of cached-node status that the verdict then appears below — finding which case failed meant piping the whole thing through grep.
Defaults to false.
--keep
Keep the build on the node afterwards instead of deleting it
Defaults to false.
--name <NAME>
Name this test run's build, so it is identifiable in bldr builds and the console instead of appearing as one more UUID. Travels as the label bldr.name=<NAME>
--label <KEY=VALUE>
Attach a label KEY=VALUE to the build (repeatable). --name is the shorthand for --label bldr.name=…
May be given more than once.
--no-cache
Re-run every function instead of using cached results (see bldr build --no-cache)
Defaults to false.
--profile
CPU-profile every pod this test run starts (see bldr build --profile)
Defaults to false.
-o, --option <KEY=VALUE>
Override a workspace option for this test run only (repeatable, see bldr build --option)
May be given more than once.