# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-jovd83-playwright-skill-tdd`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [jovd83](https://agentstack.voostack.com/s/jovd83)
- **Installs:** 0
- **Category:** [Web & Browser](https://agentstack.voostack.com/c/web-and-browser)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [jovd83](https://github.com/jovd83)
- **Source:** https://github.com/jovd83/playwright-skill/tree/main/documentation/test_cases/tdd

## Install

```sh
agentstack add skill-jovd83-playwright-skill-tdd
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# 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.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [jovd83](https://github.com/jovd83)
- **Source:** [jovd83/playwright-skill](https://github.com/jovd83/playwright-skill)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jovd83-playwright-skill-tdd
- Seller: https://agentstack.voostack.com/s/jovd83
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.