Topic · Test readiness review

What is a test readiness review, and how do I keep it true in CI?

Gist

A test readiness review is a NASA lifecycle gate: is this item ready for formal test. Proof assesses that gate from the current graph with proof gate trr, then fails the merge when a criterion is not ready.

proof gate trr

Keep Jama if you author the programme. Keep the review board if a human has to accept the campaign. Proof is not that meeting, and last month's TRR pack is not this push.

Request demo Last minutes vs this graph

01 · The dated minutes

A procedure PDF is not a TRR. Last review's minutes are not this push.

The review board looks at the article, the facility, the procedures, and whether coverage is under configuration control. A person can sign that once. The next commit does not reopen the room.

The design gate lives on preliminary design review. The SAS pack lives on software accomplishment summary. MC/DC lives on MC/DC coverage for Go. This page is the test gate: tests pass, coverage threshold, MC/DC, fixtures, Z3 properties, verification, suspect links.

TRR does not invent a test you did not write. It does not sit in the review. It does not run the campaign. Keep go test.

go test ./...
proof gate trr
proof audit --fail-level warn

The first command is still the suite. The second assesses the TRR criteria and exits 0 (ready), 1 (not ready), or 2 (ready with observations). The third is the standing merge gate. Printing last review's pack after the gate is how the minutes got stale.

02 · The exhibit

Same agenda. A date, or this graph.

The minutes still have coverage headings. The graph moved. Click the tabs.

Word / Confluence

Opened coverage from last TRR
rate_limiter still 92% in the pack

Agenda present

This push

A condition lost its independence pair. The minutes did not.

No re-assess

Word / Confluence

Still last TRR. Still a date.

Keep the review minutes

Proof

Ask does trr still pass
Exit 1 if a criterion fails

Merge blocked if the gate is not ready

Same agenda. A date, or this graph. Click the tabs.

Criterion	What the graph asks	What a green cell is not
Tests pass	`tests_pass`	Not the campaign. Keep `go test`.
Coverage threshold	`coverage_threshold`	Not line coverage as proof of the shall.
MC/DC coverage	`mcdc_coverage`	Not VectorCAST. Not LDRA. Go is in MC/DC for Go.
FLIP fixtures	`flip_fixtures_exist`	Legacy fixture-evidence only. Prefer semantic MC/DC witnesses.
Z3 properties	`z3_properties_verified`	Not every lemma. The ones you declared.
Verification	`verify_passes`	Not a DER pack. Not DO-330.
Suspect links	`suspect_clean`	Not a frozen matrix in Jama.

Formats for the assessment itself:

proof gate trr
proof gate trr --format json
proof gate trr --format markdown

Table is the default. JSON is for CI. Markdown is for a comment. TRR does not write a SAS. That pack is only proof gate sar --output sas.html on software accomplishment summary.

We have not run these gates against a frozen NASA review-board corpus, and we have not scored them against a DER pack on the same branch. The loss is named, not scored.

03 · The honest loss

A green Proof gate is not a test readiness review.

The command reports criteria on the authored model. Proof will not pretend that exit 0 is a board signature.

NPR 7150.2D still wants a human to judge whether the article, the facility, and the procedures are ready. The gate lists what you declared: tests, coverage, MC/DC, fixtures, Z3, verification, suspect links. It does not independently prove those declarations are the right campaign. Keep the TRR. Keep the minutes.

Proof is not NASA. It is not OSMA IV&V. It is not DO-330 qualified. Tests are not executed by proof gate trr. Keep go test. Jama still authors the shall. VectorCAST or LDRA still win at a qualified C toolchain.

The design gate still lives on preliminary design review. The NASA SRS still lives on NPR 7150.2D. The four jobs still live on DO-178C-style verification.

Request demo How the install is bought

04 · Nearby questions

What people type next.

What is a preliminary design review? PDR is architecture and interfaces before detailed design. That H1 lives on preliminary design review as proof gate pdr.

What is a system requirements review? SRR is the first gate. proof gate srr. Lives with PDR until it earns its own H1.

What is a critical design review? CDR is detailed design against the code annotations. proof gate cdr. Same family as PDR. Do not mint a twin from this page.

What is a software accomplishment summary? The SAR pack. That H1 lives on software accomplishment summary as proof gate sar --output sas.html.

What is MC/DC coverage? Condition independence, not line coverage. MC/DC for Go.

What is NPR 7150.2D? NASA's software engineering procedure. The SRS artefact lives on that URL. This page is the test gate, not a twin.