# Playwright Documentation Tdd

> Legacy Playwright-specific alias for TDD-style case documentation. Prefer the standalone `test-artifact-export-skill` skill for formatting approved test cases or building export-ready artifacts, and use this only when Playwright-local conventions must be preserved explicitly.

- Skill: `jovd83/playwright-documentation-tdd` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add jovd83/playwright-documentation-tdd`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jovd83/playwright-documentation-tdd/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: jovd83 (https://skillmd.com/u/jovd83)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jovd83/playwright-documentation-tdd

---


# Playwright TDD Documentation

Use this skill when the user wants structured test-case specs rather than lightweight notes.

## Output Contract

Produce one scenario document per test case with these fields:

- `title`
- `description`
- `test_suite`
- `covered_requirement`
- `preconditions`
- `steps`
- `execution_type`
- `design_status`
- `test_engineer`
- `test_level`
- `jira`
- `test_script`

Use a markdown step table with `Step`, `Action`, and `Expected result`.

## Traceability Rules

- Use repo-relative automation references such as `tests/e2e/auth/login.spec.ts#AUTH-US02-user-login`.
- Keep requirement references explicit and stable.
- If automation does not exist yet, say so instead of inventing a script link.

## Organization Rules

- Prefer feature- or story-based folders when the user wants a persistent test-doc tree.
- Keep one scenario per file when the docs are meant to be maintained over time.
- Name files after the behavior they describe, not after arbitrary numbering alone.

## Writing Rules

- Preconditions should describe the meaningful starting state, not boilerplate every test shares implicitly.
- Steps should reflect meaningful user or system actions, not every low-level click.
- Expected results should assert the requirement, not generic success language.