# Generate Scenario Tests

> Generate Playwright test files from plain English scenario descriptions in test/scenarios/ Use when this capability is needed.

- Skill: `tomevault-io/generate-scenario-tests` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add tomevault-io/generate-scenario-tests`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tomevault-io/generate-scenario-tests/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tomevault-io (https://skillmd.com/u/tomevault-io)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/tomevault-io/generate-scenario-tests

---


# Generate Scenario Tests

You are generating Playwright test files from plain English scenario descriptions.

## Process

1. Read ALL scenario files from `test/scenarios/*.md`
2. Read the shared test harness at `test/scenarios/generated/helpers.ts`
3. Read the existing generated test as a template: `test/scenarios/generated/spawn-single-session.spec.ts`
4. For each scenario file, read the relevant React components to understand:
   - What `data-testid` attributes exist (search for `data-testid` in `assets/dashboard/src/`)
   - For `<select>` controls, what the actual `<option value>` strings are (do not assume labels map to values)
   - What routes exist (`assets/dashboard/src/App.tsx`)
   - What API endpoints are called (`internal/dashboard/handlers.go`)

5. For each scenario file, generate a `.spec.ts` file in `test/scenarios/generated/`
   - File name: same as scenario file but with `.spec.ts` extension
   - Follow the exact patterns from the template test
   - Use `data-testid` selectors where available, fall back to role-based selectors
   - Include both browser assertions (Playwright expects) and API assertions (fetch calls)
   - Map `## Preconditions` to `test.beforeAll` setup
   - Map `## Verifications` to test assertions

## Rules

- Use helpers from `helpers.ts` — do NOT duplicate helper logic in tests
- Use `data-testid` selectors as the primary selector strategy
- When selecting dropdown options in Playwright, use the real option `value` (e.g. `__multiple__`), not a guessed label-derived value
- Each scenario file produces exactly one `.spec.ts` file
- Each `.spec.ts` file has one `test.describe` block with one or more `test` blocks
- Use real agent commands like `sh -c 'echo hello; sleep 600'` for test agents (mirrors `internal/e2e/e2e.go` line 240)
- Always call `waitForHealthy()` in `beforeAll`
- Always call `waitForDashboardLive(page)` after navigation
- Set reasonable timeouts for async operations (15s for spawn, 10s for WebSocket)

## Output

After generating all test files, run:

```bash
cd test/scenarios/generated && npx tsc --noEmit
```

Report any type errors and fix them before presenting the results.

## Verification

After type-checking passes, run the generated scenario tests to confirm they pass end-to-end:

```bash
./test.sh --scenarios --run '<scenario name>'
```

Replace `<scenario name>` with the test describe block name (e.g., `'Remote access onboarding'`).
If multiple scenarios were generated, run each one. Fix any failures before presenting the results.

---
> Converted and distributed by [TomeVault](https://tomevault.io/claim/sergeknystautas) — claim your Tome and manage your conversions.
<!-- tomevault:4.0:skill_md:2026-04-11 -->