Why does this skill prioritize accessibility-based queries?

Using semantic queries like 'getByRole' ensures your tests interact with the page like a real user, making them more resilient to CSS/ID changes while improving overall app accessibility.

How does this skill prevent flaky E2E tests?

It implements defensive patterns such as waiting for visibility before interaction, handling CSS animations, and using stability-verified click actions to ensure tests pass consistently.

Which testing frameworks are supported?

While the principles are universal, the skill provides specific implementation patterns for Playwright (E2E) and Vitest (Unit and Integration testing).

What is the recommended TDD workflow?

The skill follows a five-step process: write a failing test, run it to confirm failure, write minimum code to pass, confirm the pass, and finally refactor while keeping tests green.

TDD & Automated Testing

Name: TDD & Automated Testing
Author: zoonk

byzoonk

•

Security & Testing

Implements rigorous Test-Driven Development (TDD) workflows and stable automated testing patterns across unit, integration, and E2E layers.

About

This skill equips Claude with a comprehensive framework for engineering high-quality, reliable software through a 'test-first' methodology. It provides specialized guidance for creating non-flaky E2E tests using Playwright and robust unit/integration tests with Vitest, emphasizing defensive programming patterns to handle animations and async operations. By prioritizing semantic, accessibility-based queries and destination content verification, it ensures that tests are resilient to UI refactors and truly representative of user behavior while maintaining a strict Red-Green-Refactor workflow.

Key Features

Defensive Playwright patterns to eliminate flaky E2E tests caused by animations
Accessibility-first testing using semantic queries and ARIA roles
89 GitHub stars
Automated stability verification for new test suites
Full TDD workflow enforcement (Red-Green-Refactor) for features and bug fixes
Cross-layer testing coverage including Vitest integration and unit patterns

Use Cases

Refactoring frontend components while maintaining stability through high-confidence E2E suites
Developing new features with a test-first approach to ensure technical debt is minimized from day one
Fixing complex bugs by first establishing a reproducible failing test case to prevent regressions

About

Key Features

Defensive Playwright patterns to eliminate flaky E2E tests caused by animations
Accessibility-first testing using semantic queries and ARIA roles
89 GitHub stars
Automated stability verification for new test suites
Full TDD workflow enforcement (Red-Green-Refactor) for features and bug fixes
Cross-layer testing coverage including Vitest integration and unit patterns

Use Cases

Refactoring frontend components while maintaining stability through high-confidence E2E suites
Developing new features with a test-first approach to ensure technical debt is minimized from day one
Fixing complex bugs by first establishing a reproducible failing test case to prevent regressions