tdd-workflow

Enforce test-driven development with 80%+ coverage across unit, integration, and end-to-end tests.

8|1|Updated Dec 6, 2025
One-click install
npx skills add https://github.com/zzh0u/gojet --skill tdd-workflow-zzh0u
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/zzh0u/gojet/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/zzh0u/gojet --skill tdd-workflow-zzh0u

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD drives higher code quality by ensuring tests define and validate behavior before implementation, preventing regression and reducing debugging time.

Core Features & Use Cases

  • Enforces writing tests before code for new features, bug fixes, and refactoring.
  • Requires and guides achieving 80%+ test coverage across unit, integration, and end-to-end tests.
  • Provides step-by-step workflow guidance from user journeys to test execution and refactoring.

Quick Start

Define a user journey, then write failing tests and implement code to make them pass.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce test-driven development for new features and refactoring?

To enforce test-driven development, this workflow requires writing failing tests before implementation, guiding you through user journeys, test case generation, and code validation to ensure behavior is defined upfront.

What is the best way to achieve 80% test coverage across unit and e2e tests?

Achieving 80% test coverage requires running unit, integration, and end-to-end tests iteratively. This workflow guides you through generating test cases and validating code until the coverage threshold is met before feature completion.

Does this test-driven development workflow work with Playwright and Vitest?

Yes, this workflow supports tooling patterns like Jest, Vitest, and Playwright, utilizing them to validate unit, integration, and end-to-end test scenarios during the structured test-first implementation process.

How do I start writing tests first when fixing bugs?

Start writing tests first for bug fixes by defining the user journey, generating test cases that reproduce the bug, running the failing tests, and then implementing the code corrections to make them pass.

When do I need to write end-to-end tests instead of unit tests?

You need end-to-end tests when validating complete user journeys and integration points, whereas unit tests validate isolated code behavior. This workflow structures both to ensure comprehensive coverage before refactoring.