report-formatlisted

# Test Report Format ## File Conventions - **Location:** `docs/testing/reports/` - **Naming:** `YYYY-MM-DD-<topic>-report.md` where `<topic>` matches the test plan topic - **Screenshots:** `docs/testing/reports/screenshots/` (referenced from report) - **Create directories if needed:** `mkdir -p docs/testing/reports/screenshots` --- ## Report Structure Every test report MUST follow this exact structure: ~~~markdown # Test Report: <title> ## Summary - Total: <N> | Pass: <N> | Fail: <N> | Skip: <N> - Plan: <path to test plan file> - Date: <YYYY-MM-DD> - Duration: <approximate execution time> ## Issues Found ### [SEVERITY] QA-001: <issue title> **ID:** QA-001 **Location:** `<source file:line>` **Category:** Testing **Problem:** - Expected: <what should have happened> - Actual: <what actually happened> **Impact:** <what breaks if unfixed — optional but recommended> **Remediation:** <best-effort suggestion in natural language; no code block required> **Scenario:** <FE-XX or BE-XX> **Response:** `<response body or error>` (BE only) **Screenshot:** <path to screenshot> (FE only) ### [SEVERITY] QA-002: <issue title> ... ## Detailed Results ### Pass: FE-01: <scenario name> ### Pass: BE-01: <scenario name> ### Fail: BE-03: <scenario name> — see QA-001 ### Skip: FE-03: <scenario name> (reason) ~~~ --- ## Issue ID Assignment **Prefix:** `QA` (all issues use the same prefix, mapped to `Category: Testing` in the code-review Category→Prefix table) **Algorithm:** 1. Initi