tdd-workflow

Name: tdd-workflow
Availability: InStock
Author: xpgcrx

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

5|Updated Mar 15, 2025

Search Tags:#workflow #testing #tdd #integration-test #unit-test #junit #e2e-test

Ready to run

npx skills add https://github.com/xpgcrx/dotfiles --skill tdd-workflow-xpgcrx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/xpgcrx/dotfiles/tree/main/gemini/skills/tdd-workflow
Command: npx skills add https://github.com/xpgcrx/dotfiles --skill tdd-workflow-xpgcrx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

このガイドは新機能の開発・修正・リファクタリング時にテスト駆動開発を徹底させ、ユニット・統合・E2Eのカバレッジを80%以上維持することを目的とします。

Core Features & Use Cases

Tests BEFORE Code: 最小限の実装でパスするテストを先に作成する原則を適用します。
High Coverage Policy: ユニット・統合・E2Eを組み合わせた高いテストカバレッジを維持します。
Guided Workflow: ユーザージャーニーの作成、テストケースの設計、実行・リファクタリングの循環を支援します。

Quick Start

新機能の実装前にテストを作成して失敗させ、その後最小限のコードでテストを通過させる循環を実行してください。

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 workflows to maintain 80% test coverage?▼

To enforce test-driven development workflows, you must write minimal failing tests before implementation and maintain 80%+ coverage across unit, integration, and E2E tests. This approach prevents regressions during feature development, bug fixes, and refactoring.

What is the proper workflow for writing tests before code during refactoring?▼

The proper test-driven development workflow requires designing test cases first, running them to fail, then implementing minimal code to pass. During refactoring, this ensures edge cases and error scenarios are covered while maintaining high test coverage.

Does TDD workflow support unit, integration, and E2E testing simultaneously?▼

Yes, TDD workflow supports unit, integration, and E2E testing simultaneously. It enforces a high coverage policy across all three test types to ensure comprehensive validation of user journeys, edge cases, and error scenarios.

How do I organize test cases and mocking for integration and E2E tests?▼

To organize test cases and mocking for integration and E2E tests, follow a guided workflow that designs test cases around user journeys. This ensures proper test organization and effective mocking to maintain 80%+ coverage.

What's the best way to prevent regressions during feature development and bug fixes?▼

The best way to prevent regressions during feature development and bug fixes is to apply a test-driven development workflow. By specifying that tests must be written before coding and cover edge cases, you ensure implementation is driven by tests.

Why does test-driven development require failing tests before minimal implementation?▼

Test-driven development requires failing tests first to validate that the test itself is meaningful before writing minimal implementation code to pass it. This cycle ensures tests drive the implementation and prevents unnecessary code complexity.