tdd-workflow

Enforce test-driven development with unit, integration, and E2E tests at 80%+ coverage.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/hbvg234/jnmt.vn --skill tdd-workflow-hbvg234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/hbvg234/jnmt.vn/tree/main/.claude/skills/tdd-workflow
Command: npx skills add https://github.com/hbvg234/jnmt.vn --skill tdd-workflow-hbvg234

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing code often lacks consistent testing discipline, leading to fragile features and regression risk.

Core Features & Use Cases

  • Enforces 80%+ test coverage across unit, integration, and E2E tests to ensure stability.
  • Provides a structured workflow from writing tests first to refactoring with green tests.
  • Includes example test templates and patterns for unit, integration, and E2E scenarios.

Quick Start

Write a failing unit test for a new feature, then implement the minimum code to pass the test and expand tests to reach the target coverage.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce TDD workflow with 80% test coverage in my project?

To enforce TDD workflow with 80% test coverage, you must write failing unit, integration, and E2E tests before implementation, then write the minimum code to pass them and refactor while maintaining green tests.

What is the best way to structure unit, integration, and E2E testing during feature development?

The best way to structure unit, integration, and E2E testing is following a structured workflow: write tests first across all three scopes, implement code to pass them, and use example templates to ensure 80%+ coverage.

Can I use this TDD workflow for bug fixes and refactoring projects?

Yes, you can use this TDD workflow for bug fixes and refactoring projects. It requires writing failing tests to reproduce issues or validate changes before implementation, ensuring stability through 80%+ coverage thresholds.

How do I start test-driven development if my codebase lacks testing discipline?

To start test-driven development without testing discipline, write a failing unit test for a new feature, implement the minimum code to pass the test, then expand tests across integration and E2E patterns to reach the target coverage.

Does this testing workflow support unit, integration, and E2E test patterns together?

Yes, this testing workflow supports unit, integration, and E2E test patterns together. It provides example templates and enforces combined test coverage thresholds of 80%+ across all three testing scopes.