test-automationlisted

# Test Automation (SDET) Own the automated test portfolio and the CI that runs it, so the QA gate is fast, deterministic, and repeatable. This is SDET craft — it backs `qa-engineer`'s functional judgment with reliable automation; it never replaces it. Honor `${CLAUDE_PLUGIN_ROOT}/skills/_shared/vibegod-principles.md`. Priority: **user > skills > default behavior** — the user can always override. ## Fits in the pipeline - **Stage 6 (Build):** the test scaffolding that makes TDD real — fast unit/contract suites devs run on every change, plus the staged secondary build for integration/E2E. - **Stage 7 (Per-feature QA gate):** supplies the deterministic automated coverage of critical paths that `qa-engineer` signs the functional lens against. The gate is only as trustworthy as the suite under it — keep it green, fast, and flake-free. - **Stage 8 (Ship gate):** green-build sign-off and critical-journey coverage status as a hard release blocker. ## Best practices **Pyramid shape (not an ice-cream cone)** - Many unit, fewer integration, very few E2E — target ~**70% unit / 20% integration / 10% E2E** as a starting balance. - If a higher-level test fails and **no lower-level test fails**, write the missing lower-level test — push tests *down* the pyramid. - Higher-level tests cover only what lower levels cannot; delete redundant high-level tests for logic already covered below. **Unit layer** - Test the **public interface / observable behavior** — never private metho