Test cases: Health & operations
Nội dung này hiện chưa có sẵn bằng ngôn ngữ của bạn.
Document control
Section titled “Document control”| Version | Date (UTC) | Summary |
|---|---|---|
| 1.0.0 | 2026-05-13 | Initial ops-focused catalogue |
| 1.1.0 | 2026-05-13 | Readiness, metrics, SPA smoke matrix |
- Backend:
GET /api/v1/health(or configured path) — Operations troubleshooting. - Deploy: static SPAs + API Deployment.
Scenario catalogue
Section titled “Scenario catalogue”| ID | Class | Scenario | Automation |
|---|---|---|---|
| TC-OPS-001 | Happy | Health returns 200 when DB reachable | Unit + E2E* |
| TC-OPS-002 | Unhappy | Health returns 503 when DB down; load balancer drains | Manual |
| TC-OPS-003 | Happy | Post-deploy smoke: login page loads, API /docs reachable when enabled | Manual |
| TC-OPS-004 | Unhappy | Wrong DOCUMENTATION_SITE_URL → broken canonical links caught in docs build | Unit (npm run build in apps/docs) |
| TC-OPS-005 | Happy | Liveness vs readiness probes (if split) — liveness stays 200 under DB drain | Manual |
| TC-OPS-006 | Happy | /metrics or OpenTelemetry scrape target reachable when enabled | Manual |
| TC-OPS-007 | Happy | Post-deploy: admin + vendor SPA index.html + hashed asset 200 | Manual |
| TC-OPS-008 | Unhappy | API CORS misconfig on staging → browser preflight fails (catch before prod) | Manual |
Coverage checklist (this sheet)
Section titled “Coverage checklist (this sheet)”- CI pipeline stages mapped to TC-OPS ids
- On-call runbook links for 503 paths
- DR / backup restore spot-check scenarios (if product mandates)
Parent index: System test cases (index)