QA TEMPLATE / SAMPLE

QA document templates and examples

Practice traceability with a synthetic Order Book failure.

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.

Choose the document you need

Follow the stale sequence 103 overwriting current 104 from specification to Run, defect and quality report. Read an example, then copy its blank template into the engagement. There are nine documents plus this index in each language: ten English and ten Traditional Chinese static pages.

Documents	Responsibility	Entry point
00 QA Test Request	Decision question, subject, scope, authority and missing inputs.	View example · Blank template
01 Quality Risk Assessment	Risk, test depth and residual issues.	View example · Blank template
02 Test Specification	Sources, scope, risk, oracle and shared data contract.	View example · Blank template
03 Test Scenario	Scenarios, data partitions, case priority and traceability.	View example · Blank template
04 Test Case	Concrete inputs, steps, expected results and checkpoints.	View example · Blank template
05 Test Run Record	Actual results and evidence for each execution.	View example · Blank template
06 Defect Report	Expected / actual differences, impact, severity and retesting.	View example · Blank template
07 Release Quality Summary	Known issues, completion, exit decision and untested scope.	View example · Blank template
08 Dashboard Status Contract	Read-only public status derived from an approved summary.	View example · Blank template

How the documents connect

DEMO-SPEC-MDQ v1.2 / DEMO-DC-MDQ v1.0 DEMO-REQ-STALE ↔ RISK-OB-SEQ DEMO-SC-BOOK → TC-MDQ-017 v1.2 DEMO-RUN-FAIL-001 → DEF-MDQ-004 DEMO-QUALITY-MDQ: Blocked (synthetic)

The traceability matrix links to cases and defects; the defect also links back to the failed checkpoint and Run.

Apply this to your engagement

Copy the blank specification and enter actual sources and versions.
Rederive data, units, timing, expected values, stop conditions and evidence for the target product. Retain document responsibilities and traceability; changing only the product name is insufficient.
Use the Case template to define observable checkpoints. Obtain required approval before operating the product.
Record each execution in a new Run, preserving history. Use the Quality Report to derive the overall status.

Conditions still requiring confirmation

For feed protocols, account / data access, completion signals, time limits, AI use, evidence retention and exit criteria, see open questions. Equal sequences and gaps remain undefined; teaching assumptions are not exchange rules.

These forms and methods originate from the company templates. Version 1.3 completes English and Traditional Chinese reading pages for all nine documents 00–08 using the same Order Book scenario. Original project templates remain unchanged; the nine Markdown files are the canonical authoring library. QA-Lite retains brief/design, run ledger and decision as three records. HTML supports reading and copying fields without creating another status ledger.