QA TEMPLATE / SAMPLE

Test Scenario

Test scenario | Market-data flow and independent 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

Split the market-data flow into three independently assessed conditions: sequential updates, stale events and reconnect snapshots. Scenarios retain scope and selection rationale; Runs retain execution results.

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] Scenario ID / version: [ ]
[Required] Title and goal: [what a user needs to accomplish under which conditions]
[Required] Requirement / oracle version: [REQ ID, source and confirmation status]
[Required] Risk ID: [failure mode and impact]
[Required] Role, start state, action and end state: [ ]
[Required] Entry conditions / dependencies: [ ]
[Required] Scope / exclusions: [ ]
[Required] Case table: Case ID / version | purpose | data partition / boundary | Priority | automation suitability
[Required] Assess each case independently; do not merge different inputs into one result.
[Required] Open questions / affected items: [ ]
[Conditional] Scenario default Priority: [ ]; cases may override with a rationale
[Conditional] Data and operation cleanup: [ ]
[Required] Trace: Case → each Run → Defect; do not prefill an overall Scenario Pass.

Filled example

DEMO-SC-BOOK · v1.2 | Keep the Order Book current

Role: synthetic market-data consumer. Start state: SNAP-104. Supply the next event, an old event or a reconnect snapshot separately, resetting each case independently.

Requirements: DEMO-REQ-NEXT / STALE / RECONNECT; risk RISK-OB-SEQ; data contract DEMO-DC-MDQ v1.0. Default Scenario priority P1; cases may override based on risk. Record Severity separately in the defect.

Case / purpose	Data partition	Priority and automation
TC-MDQ-016 v1.2: sequential update	104 → 105; normal order.	P0 overrides P1 due to basic market-data correctness. Suitable for automation; this document supplies no executable script.
TC-MDQ-017 v1.2: reject old event	104 receives 103; representative negative-order input.	P0 overrides P1 to prevent state regression. Suitable for automation; this document supplies no executable script.
TC-MDQ-018 v1.2: recover after reconnect	104 → complete snapshot 106; state transition.	P1; suitable for automation with an explicit snapshot-applied completion signal.

Data and boundaries

103 / 104 / 105 illustrate old, baseline and next values only. Equal sequences, gaps, reorder buffering, zero quantities, missing values and events during disconnection are untested. These three cases do not establish full protocol coverage.

For real work, first resolve DEMO-Q-SEQ. If rules or observability are insufficient, mark affected cases Blocked. On rule revision, update case versions and append Runs.

Execution traceability

For steps and expectations, see Test Case; for synthetic case results, see Run Log; for known issues, see DEF-MDQ-004.