QA TEMPLATE / SAMPLE

Run Log

Execution record | Actual observations for each of three cases

Synthetic Order Book teaching scenario, not a real exchange test. Based on this site's stale-sequence Fail Demo. Prices, quantities and times are supplemental teaching assumptions. Runs, defects and evidence names are synthetic; there was no real product execution, attached evidence or customer approval.

What this document answers

A Run fixes case and contract versions and retains per-case observations and evidence. This static filled example has no execution or saving function. All three results belong to one synthetic batch.

Blank template

[Required] applies to every case. [Conditional] is required when applicable; explain when it is not. Copy the text into your case documents and replace the brackets. This static page has no editing or saving function.

Blank Run fields (check readiness before execution)
Run ID / case version / data row / attempt number: [ ]
Environment / product version / time and timezone / executor: [ ]
Readiness check and approved oracle: [ ]
Actual model / prompt / data versions: [if applicable]
Step / CP → Actual Result → Status → Evidence: [ ]
Operation / event ID / Defect ID / failed step: [ ]
Run Status: [Not Run / Pass / Fail / Blocked / Skipped]
Incomplete work, blocker and resume conditions: [ ]
In Progress is a working draft only, not an archived result.
Actual data contract ID / version: [ ]
Actual snapshot IDs, as-of / timezone, capture times: [ ]

Filled Run example

DEMO-RUN-FAIL-001 · Entirely synthetic Retains this site's Fail Demo: 3 cases, 2 Pass / 1 Fail, exit 1, total 0.83 seconds. The v1.2 document adds the data contract and checkpoints. No tests were rerun and no original Run was modified.

Field	Example value
Version / environment / people	All three teaching cases v1.2; DEMO-BOOK / build-demo-1; DEMO-TESTER (fictional).
Readiness record	The synthetic setup gives each case an independent SNAP-104, specified input and completion signal. Real specification approval and execution evidence: not supplied.
Contract / data	DEMO-DC-MDQ v1.0 / DEMO-BOOK-DATA-v1; attempt 1 per case; data rows below.
Time / snapshots	Supplemental teaching times: 2026-10-26, UTC+08:00. STALE-103 baseline as-of 17:20:11.400, captured 17:20:11.402; post-event snapshot as-of 17:20:11.519, captured 17:20:11.523. Both time types are recorded separately and are fictional.
Evidence identifiers	DEMO-EV-INPUT, DEMO-EV-BEFORE and DEMO-EV-AFTER identify the input and complete before / after snapshots for each Case / data row / attempt. They are teaching identifiers with no attachments. Failed checkpoints: CP2–CP3.
Review and defect	No human result review. TC-MDQ-017 links to DEF-MDQ-004; there is no post-fix Run.

Per-case records in the same batch

Case / version / data row	Synthetic Actual Result	Status / duration
TC-MDQ-016 v1.2 NEXT-105 / attempt 1	CP1–CP3 completed; actual sequence=105, bid 100×4, ask 101×3.	Pass (illustrative) / 0.18s
TC-MDQ-017 v1.2 STALE-103 / attempt 1	CP1 holds. CP2 accepts E-103; CP3 actual sequence=103, bid 100×9, ask 101×3 violates the expectation.	Fail (illustrative) / 0.21s
TC-MDQ-018 v1.2 RECONNECT-106 / attempt 1	CP1–CP3 completed; actual complete snapshot: sequence=106, bid 100×5, ask 101×6.	Pass (illustrative) / 0.44s

Independent case data prevents the stale-event failure from contaminating the other cases. Durations are retained from the site's synthetic example, not an SLA or performance measurement. Not started means Not Run; missing prerequisites mean Blocked; a deliberate omission means Skipped with a reason. For the overall decision, see the Quality Report.