skills.rest
fideguch
fideguchCOMMUNITY
Explore all skills by this author →
GitHub

tdd-workflow

Enforce test-driven development workflows with unit, integration, and end-to-end tests.

1|Updated Jan 30, 2021
Search Tags:#workflow#testing#tdd#quality#coverage#software-engineering
One-click install
npx skills add https://github.com/fideguch/my_dotfiles --skill tdd-workflow-fideguch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/fideguch/my_dotfiles/tree/main/claude/skills/tdd-workflow
Command: npx skills add https://github.com/fideguch/my_dotfiles --skill tdd-workflow-fideguch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures development work adheres to test-driven development practices, reducing regressions and improving maintainability by requiring tests before code and enforcing meaningful test coverage.

Core Features & Use Cases

  • Enforces writing unit, integration, and end-to-end tests before code.
  • Provides a structured workflow from defining user journeys to test creation, implementation, and refactoring.
  • Helps teams measure and maintain 80%+ overall test coverage across critical features.

Quick Start

Begin with a feature you plan to implement and generate the initial unit tests that drive the implementation.

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 and ensure 80%+ test coverage during software development?▼

You can enforce test-driven development by adopting a workflow that requires writing unit, integration, and end-to-end tests before implementation. This approach ensures 80%+ overall test coverage, reducing regressions and improving maintainability across critical features.

What is the best way to structure a TDD workflow for feature development and refactoring?▼

A structured TDD workflow moves sequentially from defining user journeys to test creation, implementation, verification, and refactoring. This ensures code development adheres to testing guidelines for both feature development and bug fixes.

When do I need to write unit, integration, and end-to-end tests in a TDD workflow?▼

You need to write unit, integration, and end-to-end tests before writing the actual code. This test-first strategy verifies behavior immediately and ensures development work adheres to test-driven development practices.

Does TDD with an 80% coverage target work for both new features and bug fixes?▼

Yes, test-driven development with an 80% coverage target is applicable to feature development, bug fixes, and refactoring. It provides clear test scaffolds to verify behavior and maintain software quality across all development tasks.

How do I start a TDD workflow for a new software feature?▼

Begin a test-driven development workflow by selecting a planned feature and generating the initial unit tests that drive the implementation. This establishes the required test scaffolds before moving to code creation and verification.

Related Skills

Explore More Software Engineering Skills→
Ying-Kai-LiaoYing-Kai-Liao
1

tdd-workflow

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

Community
Advanced
SOLEROMSOLEROM

tdd-workflow

Enforce test-driven development with tests before code and 80%+ coverage validation.

Community
Intermediate
onbluerosesonblueroses
3

tdd

Automate Test-Driven Development cycles by generating tests for code features.

Community
Intermediate
JamkrisJamkris
86

tdd-workflow

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

Community
Intermediate