e2e-test-writerlisted

Generates end-to-end tests from scenario-set.md. Web target → Playwright; mobile target → Detox. Every test imports a Page Object (never touches raw selectors), uses a named auth strategy, waits on observable conditions (never sleeps), and preserves scenario ids as trace anchors. Gate contract — zero raw selectors in the test body, zero sleep-based waits, zero xpath selectors. PIPELINE-3 step 2.
mytechsonamy/VibeFlow · ★ 0 · Testing & QA · score 75

Install: claude install-skill mytechsonamy/VibeFlow

# E2E Test Writer An L2 Truth-Execution skill. Its job is to turn scenarios into **runnable, non-flaky end-to-end tests**. The skill's main enemy is not "writing more tests" — it's writing tests that silently lie: pass on your machine, fail in CI, and waste hours to triage. The three rules below are non-negotiable because each one is a common root cause of e2e flake. ## When You're Invoked - During PIPELINE-3 step 2, after `test-strategy-planner` has produced `scenario-set.md` and the target platform is declared in `vibeflow.config.json`. - On demand as `/vibeflow:e2e-test-writer <scenario-glob>`. ## Input Contract | Input | Required | Notes | |-------|----------|-------| | `scenario-set.md` | yes | Output of `test-strategy-planner`. Only scenarios tagged for the declared platform become candidates. | | Platform | yes | `web` / `ios` / `android`. Drives which `platform-recipes.md` section loads (Playwright for `web`, Detox for `ios`/`android`). | | Target location | yes | `web` → base URL; `ios`/`android` → bundle identifier. Never hardcoded — read from arg or from `vibeflow.config.json.targetLocations`. | | Auth strategy catalog | derived | `references/pom-patterns.md` defines the 4 named strategies. The scenario names the one it needs. | | Existing Page Objects | scanned | Imported when they match the scenario's target screen. Hand-written POMs are never rewritten — this skill only reads them. | | `repo-fingerprint.json` | optional | Used to confirm the project's a