tdd-workflow

Enforce a TDD workflow with 80% coverage across unit, integration, and E2E tests.

Updated Jun 2, 2025
One-click install
npx skills add https://github.com/wraithyy/dotfiles --skill tdd-workflow-wraithyy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/wraithyy/dotfiles/tree/main/dot_claude/skills/tdd-workflow
Command: npx skills add https://github.com/wraithyy/dotfiles --skill tdd-workflow-wraithyy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) process to ensure high-quality, well-tested code, reducing bugs and improving maintainability.

Core Features & Use Cases

  • TDD Enforcement: Guides users to write tests before writing implementation code.
  • Comprehensive Coverage: Mandates 80%+ coverage across unit, integration, and E2E tests.
  • Structured Workflow: Provides clear steps for writing user journeys, generating tests, implementing code, and refactoring.
  • Use Case: When developing a new API endpoint, use this skill to first define tests for expected success, error, and edge cases, then write the minimal code to pass those tests, ensuring robustness.

Quick Start

Use the tdd-workflow skill to guide the development of a new feature, starting with writing tests before implementation.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I start test-driven development for a new JavaScript API endpoint?

Test-driven development for a JavaScript API endpoint starts by writing tests for expected success, error, and edge cases before writing any implementation code, ensuring minimal code is then added to pass those tests.

How do I ensure 80% code coverage across unit, integration, and E2E tests?

To ensure 80% code coverage, you must write tests covering user journeys, edge cases, and error scenarios across unit, integration, and end-to-end tests using frameworks like Jest and Playwright before implementing the code.

What is the correct TDD workflow for writing tests before implementation code?

The correct TDD workflow involves defining user journeys, generating tests for expected behaviors, writing the minimal implementation code to pass those tests, and finally refactoring the codebase while maintaining high code quality.

Can I use Jest and Playwright together for comprehensive JavaScript test coverage?

Yes, you can use Jest and Playwright together to enforce comprehensive test coverage, utilizing Jest for unit and integration tests while relying on Playwright to handle end-to-end user journey validations.

When should I not use a strict test-first development approach?

A strict test-first development approach may not suit exploratory prototyping or throwaway scripts where immediate functional validation is prioritized over maintaining 80% code coverage and long-term maintainability.

Why does writing tests first improve code quality and reduce bugs?

Writing tests first improves code quality by enforcing a rigorous Test-Driven Development process that defines exact expected behaviors, edge cases, and error scenarios upfront, thereby reducing bugs and improving maintainability.