skills.rest
ChanningHe
ChanningHeCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

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

Updated Jan 1, 2026
Search Tags:#testing#tdd#e2e#unit-testing#integration-testing#software-quality
One-click install
npx skills add https://github.com/ChanningHe/dotfiles --skill tdd-workflow-channinghe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/ChanningHe/dotfiles/tree/main/claude/skills/tdd-workflow
Command: npx skills add https://github.com/ChanningHe/dotfiles --skill tdd-workflow-channinghe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enforces test-driven development, ensuring code is written only after defining tests and targeting 80%+ test coverage across unit, integration, and E2E levels.

Core Features & Use Cases

  • Enforces the 'tests before code' principle to guide feature development, bug fixes, and refactors.
  • Provides a structured 3-tier test approach covering unit, integration, and E2E validation for reliable software delivery.
  • Example use case: a developer writes new functionality, creates tests first, then implements minimal code to pass tests while expanding coverage.

Quick Start

Write tests first for new or changing functionality, then implement code to fulfill the tests and achieve the desired 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 test-driven development for new features and bug fixes?▼

You enforce test-driven development by writing tests before implementing code for new features, bug fixes, and refactors, then validating the results against those tests.

What is the best way to achieve 80% test coverage across unit, integration, and E2E tests?▼

Achieve 80% test coverage by applying a structured 3-tier testing approach across unit, integration, and E2E validation, using automated test runs and coverage analysis to measure outcomes.

Can I use this workflow for both feature development and refactoring existing code?▼

Yes, this workflow applies to feature development, bug fixes, and refactors by ensuring you define tests first, then implement minimal code to pass them while expanding coverage.

How do I measure test coverage outcomes after writing tests first?▼

Measure test coverage outcomes via automated test runs and coverage analysis to ensure your codebase meets the minimum 80% coverage threshold across all testing scopes.

Do I need a defined testing strategy before starting test-driven development?▼

Yes, test-driven development requires a defined testing strategy to guide the 3-tier test approach and ensure measurable outcomes across unit, integration, and E2E scopes.

Related Skills

Explore More Software Engineering Skills→
SuperlendSuperlend

wycheproof

Validate cryptographic implementations against known attacks and edge cases.

Official
Advanced
thechandanbhagatthechandanbhagat
8

test

Generate pytest and Jest unit tests, integration tests, and mock data.

Community
Basic
aimskraimskr

testing-strategy

Design test strategies and QA plans for software features.

Official
Intermediate
fahchenfahchen

discovery

Guide interactive BDD discovery sessions and generate Gherkin .feature files.

Community
Advanced