Skip to content
Registry StackDocsv0.46.0

evidencectl test command reference

View as Markdown

Run the project’s synthetic Evidence fixtures.

This page is generated from the public Clap command tree for Registry Stack source version 0.46.0 and catalog SHA-256 d43b1bf418e0b00fac52311fa3a106fa124512dbc88cf511475713af2d73aa47. Hidden implementation commands are omitted.

evidencectl test [OPTIONS] <PROJECT>
ConditionRequirement
--case <CASE> is present--fixture <FIXTURE> is required.
ArgumentAlways requiredDefaultValuesEnvironmentDescription
<PROJECT>Yesn/an/an/aEditable or deployment Evidence project directory
OptionAlways requiredDefaultValuesEnvironmentDescription
--target <TARGET>Non/an/an/aComplete deployment target to use when compiling an editable project
--fixture <FIXTURE>Non/an/an/aRun only the exact bundle-relative fixture path named here
--case <CASE>Non/an/an/aRun only the exact case identifier in the selected fixture
--explainNon/an/an/aInclude the runtime’s structured value-free evaluation trace
--deny-warningsNon/an/an/aExit 1 when a warning is reported
--format <FORMAT>Nohumanhuman, json, junitn/aEmit the selected command’s report in this format. junit is accepted only by test and fixtures run
-h, --helpNon/an/an/aPrint help

After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.