Run Result
Fail3 Cases · 2 Pass · 1 FailSynthetic scenario / Not current CEX evidence
Test Case Fail Demo
Synthetic teaching scenario · counterfactual steps
Decision replay
A failure, its fix and a passing test answer different questions. Explore the decision boundary without changing real records.
Required case failed · No-Go
Fix the defect and perform a targeted rerun. The original failure remains in the ledger.
synthetic-failureDecision impact
How does one required-case failure affect the decision?
Product Status
At RiskP0 risk not acceptedRelease Decision
Do not releaseRemain No-Go until fixed and rerunLinked Defect
DEF-MDQ-004High · OpenSynthetic run record
WebSocket ordering checks
TC-MDQ-016Accept sequentially increasing market-data updates
P00.18sPassTC-MDQ-017Reject stale-sequence updates
P00.21sFailTC-MDQ-018Restore the latest snapshot after reconnecting
P10.44sPass×TC-MDQ-017 failure detailsOpen by default so material risk is not hidden
Expected
Reject the stale-sequence updateAfter sequence 104, sequence 103 must not overwrite current data.Actual
The stale update was acceptedSequence 103 overwrote 104, returning the order book to stale state.Impact
Users may see stale market dataRisk
High · Release blockingReproduction
Failed 3 of 3 timesLinked defect
DEF-MDQ-004 · Stale update overwrites current state
- Status
- Open
- Severity
- High
- Owner
- William (Demo)
- Next
- Fix → targeted rerun → release re-assessment
Sanitized execution output
Execution Log
Only logs directly supporting the failure decision are shown; secrets, internal paths, and unrelated output were removed.
- INFO
case=TC-MDQ-017 start current_sequence=104 - ASSERT
expected=reject actual=accepted incoming_sequence=103 - ERROR
stale update replaced current order-book state - INFO
result=FAIL defect=DEF-MDQ-004
View raw log excerpt
FAILED tests/test_order_book.py::test_rejects_stale_update
AssertionError: stale sequence 103 was accepted after sequence 104
Expected: update rejected and current state preserved
Actual: stale update replaced current state
1 failed, 2 passed in 0.83sReading rules
- Test Case FailRecords the actual failure of one check.
- Run FailThis Run contains at least one case that did not meet acceptance criteria.
- Release No-GoThis case is a required P0 and its risk is not accepted; not every failure automatically produces the same release decision.