QA TEMPLATE / SAMPLE

00 QA Test Request

Test request | Scope, decision question and authority

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

00 Test Request defines what to test, why, and who can decide. Keep needs-information when inputs are missing; unconfirmed requirements do not establish an executable test scope.

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.

[Required] Request ID / version, document status: [ ]
[Required] Requester / QA owner, requested and target decision times: [ ]
[Required] Decision question, business objective, affected users / assets, why decide now: [ ]
[Required] Repository / release / branch / candidate full SHA: [ ]
[Required] Change summary, requested scope, explicit exclusions: [ ]
[Required] Known risks / defects / dependencies / assumptions and evidence: [ ]
[Required] Environment / platform, data and access constraints: [ ]
[Required] Available requirements / design, issue / PR, runbook, previous test evidence: [ ]
[Required] Time, people, environment and other limits: [ ]
[Required] Disclosure classification, sanitization, prohibited fields: [ ]
[Required] Intake: accepted / needs-information / rejected; risk tier, missing inputs, owner / review time: [ ]
[Required] Questions: Q ID | source / version | question | owner | affected IDs | answer source / date | new criteria / recheck: [ ]
[Required] Account / operation limits, AI service / data transfer, retention / cleanup authority: [ ]
Unknown does not grant permission. Reassess affected items after answers arrive and preserve historical results.

Filled example: market-data sequence test request

Field	Synthetic example
Request / accountability	DEMO-REQUEST-MDQ v1.3; DEMO-REQUESTER / DEMO-QA (fictional roles); requested 2026-10-26, target decision time pending.
Decision question	Which market-data tests address stale updates overwriting current state, and what is needed before release review? The objective is to prevent downstream readers from receiving a regressed Order Book. No real order or loss is claimed.
Subject / change	Teaching subject DEMO-BOOK / build-demo-1. The real target repo, branch, candidate SHA and code change are Unknown. This site's SHA must not stand in for the tested product version.
Scope / exclusions	Include sequential updates, stale-event rejection and reconnect snapshots. Exclude real feeds, orders, executions, assets and load testing.
Available data / sources	This site's synthetic TC-MDQ-016 through 018 and DEF-MDQ-004 are teaching sources. Real official feed specifications, issue / PR, operating runbook, version and valid test evidence are still required.
Risk / dependencies	RISK-OB-SEQ; requires an isolated fixture, sequence oracle, completion signal and snapshot access.
Limits / authority	This example reads synthetic data only and connects to no external service. Real accounts, operation budgets, AI services / readable data, evidence location / retention and cleanup require approval. Staffing and delivery time are not committed.
Disclosure / intake	The teaching material may be public. Do not add accounts, credentials, private data or internal links. Real test intake remains needs-information, risk tier Unknown; no human acceptance or review has occurred.

Open questions and handoff

DEMO-Q-SEQ asks the product / integration owner to confirm the feed protocol, ordering and completion signal; all three cases and DEMO-DC-MDQ are affected. Also confirm the real subject, data authority, decision date and accountable owner. Record the source version and date, then revisit Risk Assessment and Test Spec; existing Runs retain their original criteria versions.