tdd-workflow

Name: tdd-workflow
Availability: InStock
Author: fabio29t

Guide Test-Driven Development workflows with 80% coverage across unit, integration, and E2E tests.

Updated Mar 4, 2026

Search Tags:#unit tests #testing #tdd #refactoring #integration tests #code coverage #e2e tests

Ready to run

npx skills add https://github.com/Fabio29T/Everything-Claude --skill tdd-workflow-fabio29t

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/Fabio29T/Everything-Claude/tree/main/.agents/skills/tdd-workflow
Command: npx skills add https://github.com/Fabio29T/Everything-Claude --skill tdd-workflow-fabio29t

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enforces a rigorous Test-Driven Development (TDD) process to ensure high-quality, well-tested code with a minimum of 80% coverage across unit, integration, and E2E tests.

Core Features & Use Cases

Enforces TDD: Guides users to write tests before writing implementation code.
Comprehensive Coverage: Mandates 80%+ coverage, including unit, integration, and E2E tests.
Structured Workflow: Provides clear steps for defining user journeys, generating tests, implementing code, and verifying coverage.
Use Case: When developing a new API endpoint, use this skill to first define the integration tests for success, failure, and edge cases, then write the minimal code to pass those tests, and finally verify coverage.

Quick Start

Activate the tdd-workflow skill to write tests for a new feature, ensuring all tests pass and coverage exceeds 80%.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema

How do I start writing tests before implementation code using TDD?▼

To start TDD, define user journeys and generate tests for success, failure, and edge cases first. You then write minimal implementation code to pass those tests, ensuring structured test generation and verification before shipping.

What is the minimum code coverage required for unit, integration, and e2e tests?▼

The minimum code coverage required is 80 percent across unit, integration, and e2e tests. This threshold is enforced during the verification step to ensure comprehensive test coverage and high code quality before shipping.

Can I use mocking strategies for isolated testing within this TDD workflow?▼

Yes, you can use various testing patterns and mocking strategies for isolated testing. This allows you to verify code behavior independently by replacing dependencies, ensuring the TDD workflow supports comprehensive and isolated test execution.

What's the best way to structure a TDD workflow for a new API endpoint?▼

The best way to structure TDD for an API endpoint is to first define integration tests for success, failure, and edge cases. Then, write minimal code to pass those tests, and finally verify that coverage exceeds 80 percent.

Does this TDD approach support automated test generation and verification?▼

Yes, this TDD approach provides clear steps for test generation, implementation, and verification. It guides you through defining user journeys, generating tests, writing code to pass them, and verifying that coverage exceeds 80 percent.