olef verify

Generated from Olef 3.0.2. All commands · Capabilities and requirements

These entries describe available commands, not a sequence to run. Check prerequisites before changing app, device, or cloud state. Global options are listed in the command catalog.

olef verify

Plan verification and inspect test evidence with explicit coverage

olef verify --help

Output: json.

Examples from the CLI (replace sample packages, selectors, and paths with your own):

olef verify plan validate verification.json
olef verify junit --report TEST-app.xml --selection all --out baseline.json

olef verify run

Execute a bounded plan and preserve immutable per-check evidence

olef verify run --help

Output: json.

Argument	Description
<plan>	Required.
--out <OUT>	Required. New evidence directory outside the source root
--host-only	Run only host adapters; refuse all device and instrumentation checks
--json	Accepted for compatibility; output is always JSON.

Examples from the CLI (replace sample packages, selectors, and paths with your own):

olef verify run verification.json --host-only --out /tmp/verification-run

olef verify report

Read a saved run and recheck source/plan and evidence hashes without a device

olef verify report --help

Output: json.

Argument	Description
<run>	Required.
--json	Accepted for compatibility; output is always JSON.

olef verify recover

Release an interrupted run’s source/build ownership after external-worker review

olef verify recover --help

Output: json.

Argument	Description
<run>	Required.
--external-workers-stopped
--json	Accepted for compatibility; output is always JSON.

olef verify plan

Validate requirement coverage, adapter inputs and dependency ordering offline

olef verify plan --help

Output: json.

Examples from the CLI (replace sample packages, selectors, and paths with your own):

olef verify plan validate verification.json
olef verify junit --report TEST-app.xml --selection all --out baseline.json

olef verify plan validate

Validate schema version 1 without connecting to a device or running tests

olef verify plan validate --help

Output: json.

Argument	Description
<plan>	Required.
--json	Accepted for compatibility; output is always JSON.

Examples from the CLI (replace sample packages, selectors, and paths with your own):

olef verify plan validate verification.json
olef verify junit --report TEST-app.xml --selection all --out baseline.json

olef verify junit

Parse saved JUnit reports. This is an observation, not proof of a fresh execution

olef verify junit --help

Output: json.

Argument	Description
--report <REPORT>	Required. XML reports; each expected report must be present and complete
--selection <SELECTION>	Required. Stable description of the test selection, used for baseline comparisons
--minimum-tests <MINIMUM_TESTS>	Minimum expected number of test cases; empty suites never pass Default: 1.
--out <OUT>	Save the normalized report for later baseline comparison
--json	Accepted for compatibility; output is always JSON.

Examples from the CLI (replace sample packages, selectors, and paths with your own):

olef verify plan validate verification.json
olef verify junit --report TEST-app.xml --selection all --out baseline.json

olef verify compare

Compare two normalized reports without silently discarding missing tests

olef verify compare --help

Output: json.

Argument	Description
--baseline <BASELINE>	Required.
--candidate <CANDIDATE>	Required.
--json	Accepted for compatibility; output is always JSON.

Examples from the CLI (replace sample packages, selectors, and paths with your own):

olef verify plan validate verification.json
olef verify junit --report TEST-app.xml --selection all --out baseline.json