git:20260512.fbc88a7 to git:20260512.8e35c6b

+ 2. **Pick test type** per `Test Type Selection` below — unit, integration, or e2e (NOT default to unit)

+ 3. **Analyze target** — read file, identify testable units, list deps to mock

+ 4. **Write tests** — TDD: RED (failing) → GREEN (implement) → refactor. Existing code: passing → edge cases → errors

+ 5. **Verify coverage** — run with coverage flag, check against targets. For e2e, also confirm the runner actually executed (e.g. `npx playwright test` printed pass/fail per spec, not just "0 tests found")

+ ## Test Type Selection (decide BEFORE writing)

+

+ The default in v3.7.0 → v3.7.3 was implicitly "unit test only" because the framework table didn't list Playwright and no rule prescribed e2e. v3.7.4 fixes this:

+

+ ```toon

+ test_pyramid[3]{level,trigger,framework,when_required}:

+ unit,"Pure functions · business logic · isolated components","jest|vitest|pytest|phpunit|go test","always — fast feedback, mocks externals"

+ integration,"Multi-module interaction · DB queries · API contracts","Same runner + real DB/fakes","whenever ≥ 2 modules cross-talk"

+ e2e,"User flows · login/checkout/critical paths · cross-page nav","playwright|cypress|detox","UI/auth/payment task OR Phase 2 contract mentions 'flow' / 'journey' / 'end-to-end'"

+ ```

+

+ **Trigger words in the task description that REQUIRE an e2e layer in Phase 2:**

+

+ - `login`, `signup`, `checkout`, `payment` — critical user flows must have at least one e2e spec

+ - `flow`, `journey`, `end-to-end`, `happy path`, `smoke test`

+ - UI-bearing tasks where the artifact is a page/screen (route, view, screen)

+ - Tasks anchored to a T2 Feature whose `acceptance` references user-visible behavior

+

+ When in doubt for a UI task, **write BOTH**: unit tests for the component logic + at least one e2e spec for the happy path. Skipping the e2e layer is the silent failure mode of v3.7.0–v3.7.3 and is exactly what this section exists to prevent.

+

+ If the project has no e2e runner configured yet:

+

+ 1. Detect via repo scan: presence of `playwright.config.*`, `cypress.config.*`, `.detoxrc.js`, `e2e/` directory.

+ 2. If none, surface to the user: *"Project has no e2e runner. Install playwright (recommended) or skip e2e tests with explicit user confirmation? Say `install playwright`, `use cypress`, or `unit-only` to proceed."*

+ 3. Do NOT silently drop the e2e layer — the user must explicitly approve unit-only.

+

+ avoid[6]{pattern,fix}:

+ Unit-only for UI/auth/payment tasks,"Add an e2e layer (playwright) — silent v3.7.0–v3.7.3 default fixed in v3.7.4"

+ frameworks[8]{framework,layer,file_pattern,runner,config}:

+ Jest/Vitest,unit,"*.test.ts *.spec.ts","npm test / npx vitest","jest.config.* / vitest.config.*"

+ PHPUnit,unit,"*Test.php","./vendor/bin/phpunit","phpunit.xml"

+ Pytest,unit,"test_*.py","pytest --cov=.","pytest.ini / pyproject.toml [tool.pytest]"

+ Go,unit,"*_test.go","go test -cover ./...","go.mod"

+ Playwright,e2e,"*.spec.ts (inside tests/ or e2e/)","npx playwright test","playwright.config.*"

+ Cypress,e2e,"*.cy.ts (inside cypress/e2e/)","npx cypress run","cypress.config.*"

+ Detox,e2e (mobile),"*.e2e.ts","detox test",".detoxrc.js"

+ Vitest browser mode,integration,"*.browser.test.ts","npx vitest --browser","vitest.config.* with browser block"

+

+ **Playwright is the v3.7.4+ recommended e2e default** — it ships an MCP server (`playwright`) on the `tester` agent's allowlist, supports all 3 major browsers, and integrates with the `vitest` MCP for one-tool test execution. Cypress and Detox remain supported.

+

+ **Runner verification — never trust silence.** After `npx playwright test` / `npx cypress run`, read the actual output: did it list specs, did pass/fail counts appear, is the exit code 0? "Tests passed" without seeing pass count = `0 tests collected` = bug. Same discipline applies to all runners.