# docs/testing — P5 and master E2E test documentation

**Handoff / new AI context:** See **docs/SSOT-AND-HANDOFF.md** first, then this folder.

**For AI or human runners:** Read **MASTER-E2E-PLAN.md** for strategy (full capability, rounds, machines, gap analysis). Then use **P5-full-test-guide.md** for execution (steps, recap, report-back).

**What we're testing:** We emulate an **actual external user**. No hack job — the runner uses llmhosts.com as the source of truth, does what the app says, gets the API key from the app (Dashboard → API Keys), installs and runs the CLI per the product, and we validate that **full application capability** (every dashboard route, every CLI command, proxy, router, cache, discovery, marketplace, billing) is **harmonious and seamless**. Test account (brendonurban@gmail.com); password from project owner for login only. Everything else from the app and the product.

| File | Role |
|------|------|
| **MASTER-E2E-PLAN.md** | **Strategy.** Full capability index (§3), Round 1 (Alienware-first), Round 2 (Mac Mini, multi-GPU, large GPU), gap analysis, GitHub SSOT. Read first for "what we're proving" and "what's next." |
| **P5-full-test-guide.md** | **Execution.** Part A (site), Part B (Alienware battery + Phase 0), Part C (recap + Unresolved + Suggestions). Single source of truth for step-by-step runs. |
| P5-external-connectivity-runbook.md | Scenario/codebase reference; execution and recap → P5 full test guide. |
| P5-external-connectivity-human-checklist.md | Abbreviated Alienware flow; full steps and recap → P5 full test guide. |
| P5-external-connectivity-results-template.md | Optional per-step log; recap format and filename → P5 full test guide Part C. |
| cli-e2e-report.md | CLI E2E report (separate from P5). |

**Rounds:** Round 1 = Alienware (one GPU) — maximize every use case and edge case; all failures → GitHub → fix → re-run to 100%. Round 2 = Mac Mini (OS diversity), multi-GPU (2×4090s), large GPU (e.g. Spark 128K) for regression + new scenarios. Then gap analysis for production-ready.

**Deliverable:** Datetime-stamped recap per Part C (filename `P5-test-run-YYYY-MM-DDTHHmmss.md`) with Unresolved issues and Suggestions; report-back to project owner → dev agent.
