skills.rest
pax-k
pax-kCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

tdd-playwright-workflow

Automate TDD workflows with unit tests and Playwright end-to-end tests.

3|Updated Jun 8, 2026
Search Tags:#testing#tdd#unit testing#playwright#e2e testing
One-click install
npx skills add https://github.com/pax-k/pax-fullstack-harness --skill tdd-playwright-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-playwright-workflow
Source: https://github.com/pax-k/pax-fullstack-harness/tree/main/skills/tdd-playwright-workflow
Command: npx skills add https://github.com/pax-k/pax-fullstack-harness --skill tdd-playwright-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, and includes scripts (resource) components.

What problem does it solve?

This Skill automates test-driven development (TDD) workflows with unit tests and browser end-to-end (e2e) tests using Playwright, streamlining the process of creating and validating code changes.

Core Features & Use Cases

  • Automated Testing: Execute unit tests and Playwright e2e tests to validate code changes.
  • TDD Workflow: Supports TDD by requiring tests before implementation, ensuring test coverage.
  • Use Case: When developing a new feature, you can use this Skill to write a failing test that reproduces the behavior, implement the minimum code to pass the test, and then add e2e tests for browser workflows.

Quick Start

Use the tdd-playwright-workflow skill to create a unit test for a bug fix in the 'bug-reproduction.spec.ts' file.

Frequently Asked Questions about tdd-playwright-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a TDD workflow with unit tests and Playwright e2e tests?▼

Automate TDD workflows by writing a failing unit test to reproduce behavior, implementing the minimum code to pass, and adding Playwright e2e tests for browser workflows to ensure code coverage.

What's the best way to structure test-driven development when adding a new browser feature?▼

Structure test-driven development by first writing a failing test that reproduces the desired behavior, implementing the minimum code required to pass the test, and then validating browser workflows with Playwright e2e tests.

Do I need Playwright installed to automate e2e testing for TDD?▼

Yes, Playwright is required as a dependency. The workflow uses Playwright specifically to automate and execute browser end-to-end tests, validating code changes alongside your unit testing framework.

How does automated testing validate code changes during development?▼

Automated testing validates code changes by executing unit tests and Playwright e2e tests sequentially. This ensures both backend logic and browser workflows pass before implementation is considered complete.

Can I use this automated TDD workflow to reproduce a specific bug fix?▼

Yes, you can use the workflow to reproduce a bug fix by creating a failing test in a specific file like 'bug-reproduction.spec.ts', then implementing the code changes needed to make the test pass.

Why should I write a failing test before implementing code in a TDD workflow?▼

Writing a failing test before implementation ensures the test accurately reproduces the desired behavior. This approach enforces test coverage and validates that the minimum code implemented actually resolves the issue.

Related Skills

Explore More Software Engineering Skills→
OutlineDrivenOutlineDriven
34

design-by-contract

Generate Design-by-Contract annotations for functions across multiple programming languages.

Official
Intermediate
hidonguyenhidonguyen

ck:test

Execute unit, integration, e2e, and UI tests across JavaScript/TypeScript, Python, Go, Rust, and Flutter projects.

Community
Advanced
lehuuhau1231lehuuhau1231

lint-and-validate

Run linting and type checking across multiple programming ecosystems.

Community
Intermediate
influxdatainfluxdata
80

cypress-e2e-testing

Run Cypress E2E tests against Hugo documentation pages on port 1315.

Official
Intermediate