AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Playwright Documentation Tdd

skill-jovd83-playwright-skill-tdd · by jovd83

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.

↗ Repository
— No reviews yet
0 installs
31 views
0.0% view→install

Install

$ agentstack add skill-jovd83-playwright-skill-tdd

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-jovd83-playwright-skill-tdd)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
○ 4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Playwright Documentation Tdd? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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.

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

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Web & Browser