Coverage & Matching Metrics
High-level overview of test outcomes and requirement validation results.
- 0/0 of tests passed
- Key gaps / risks:
- No raw report in repo — Cannot assert green/red per TC without TestSprite cloud output or a regenerated
raw_report.md. - Tunnel 503 — Risk of partial or no remote execution against localhost; verify network and tunnel status before release gating.
- Dev server cap — TestSprite warns that development mode limits high-priority tests (~15); use preview/production serve for fuller runs.
- Enrichment route coverage — Manual or new automated cases should cover approve/reject, bulk actions, and
send-enrichedagainst a test API +OPENAI_API_KEYstub or mock environment.
Next step for a definitive report: re-run TestSprite when the tunnel shows connected, then replace sections 2–3 with extracted pass/fail rows from
testsprite_tests/tmp/raw_report.mdif present. - No raw report in repo — Cannot assert green/red per TC without TestSprite cloud output or a regenerated
Requirement
Total Tests
Passed
Failed
R1 — Authentication and protected routes
0
0
0
R2 — Campaigns, builder, and enrichment
0
0
0
R3 — Contacts, lists, templates
0
0
0
R4 — Analytics and transactional
0
0
0
R5 — Test execution infrastructure
0
0
0
Requirement Validation Summary
Detailed test results and validation status for each functional requirement.
R1 — Authentication and protected routes
0/0
Proper error handling for API calls and invalid data scenarios.
R2 — Campaigns, builder, and enrichment
0/0
Proper error handling for API calls and invalid data scenarios.
R3 — Contacts, lists, templates
0/0
Proper error handling for API calls and invalid data scenarios.
R4 — Analytics and transactional
0/0
Proper error handling for API calls and invalid data scenarios.
R5 — Test execution infrastructure
0/0
Proper error handling for API calls and invalid data scenarios.