e2e-write

/qa-e2e-write: Test Suite Generation

Turn test cases into a passing, re-runnable, flake-free suite. Reads playwright/AUTOMATION.md (decisions) and the POM + inventory from /qa-e2e-pom. The vocabulary is the POM and API client; the specs carry intent only.

Code standards: read {{REFERENCE_PATH}}/playwright-patterns.md before writing client, fixture, or spec code — templates (disposal context, worker-indexed accounts, network sync), the matcher table, and the anti-pattern list live there. The Phase 5 lint enforces its NEVER section. Then the project learnings file (per the preamble) — active LRN- entries scoped here override those patterns.

Constraints

1. Never invent a locator. Specs and helpers use POM exports only. A page without a POM → invoke the /qa-e2e-pom skill (build mode) and continue after its gate passes. Writing getByTestId(...) for an unmapped element inline is the defining failure of this skill.
2. Specs are intent-only. No page.locator(, no raw CSS/XPath, no page.route( in spec files — selectors live in the POM, routes/requests in the API client or fixtures.
3. Preconditions via API, not UI. Seed state with the API client. UI seeding only where no API call was observed for the operation — and flag it as debt in the report.
4. Parallel-safe data. Entity names need worker+repeat entropy — Date.now() alone collides when concurrent workers or --repeat-each instances hit the same millisecond (caught live 2026-08-07). Use a helper: `${prefix}-${Date.now()}-w${workerIndex}r${repeatEachIndex}`. Never assert global counts (before + 1) — assert your entity by name/id. The suite runs with ≥2 workers (AUTOMATION.md records the count and the isolation strategy) — tests touching the shared-state features setup flagged go in the dependent global-state project, never the parallel one.
5. Clean up what you create, through public API. Disposal context or afterEach/afterAll — never inline at the test body's end (skipped on failure), and never via test-env-only hooks (e.g., a reset endpoint): suites must survive on environments that don't have them.
6. State-based waits only. No waitForTimeout. Actions that trigger async fetches get two-stage waits: waitForResponse (promise created BEFORE the action) → then assert the rendered element. Response received ≠ rendered.
7. Never race auto-disappearing UI. Toasts and transient banners: assert the durable outcome (row exists / count via entity) instead, or catch the toast with a web-first assertion immediately after the triggering action — never after another wait.
8. No red gate, no DONE. Honest status is a gate of its own (Phase 5).