You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
2.3 KiB
2.3 KiB
Phase 7 Testing Checklist
1. Unit Tests
- Stage promotion rule evaluator returns correct decision for boundary cases.
- Stage rollback triggers on each configured rollback condition.
- Release classifier maps change categories correctly.
- Drift calculators handle missing data and sparse windows.
- Attribution joins are stable when optional overlay data is absent.
- Incident severity routing produces correct escalation path.
- Config hash and release id are attached to runtime records.
2. Integration Tests
- Create a mock stage transition request and verify approval, persistence, and activation.
- Trigger freeze condition from drift metrics and verify stage freeze is enforced.
- Trigger rollback after simulated Sev-1 incident and verify exposure constraints update.
- Submit a mock release record and verify runtime references pick up the correct active version.
- Close a trade and verify post-trade review ticket is created automatically.
- Reconcile a day of trades and verify attribution report includes stage and config references.
3. Replay / Scenario Tests
- Replay a benign week and confirm no false freeze events.
- Replay a week with stale data and verify no-trade or freeze behavior occurs.
- Replay a sequence with parser drift and verify review queue and alerts increase.
- Replay degraded fill quality and verify execution drift alerts trigger.
- Replay performance under expected drawdown and confirm no improper rollback.
4. Ops / Failure Tests
- Emergency no-trade command disables new orders without corrupting state.
- Emergency rollback to prior stage is logged and survives restart.
- Release activation failure falls back to previous known-good configuration.
- Incident creation and closure workflow can be completed without manual database edits.
- Missing report input data produces a degraded report, not a crash.
5. Acceptance Checklist
- All stage changes are auditable.
- Daily drift snapshot exists for every trading day in the test window.
- At least one daily, weekly, and monthly report can be reproduced exactly.
- Operator runbook steps were executed in a dry run.
- Freeze and rollback logic was validated by scenario test.