tdd

Enforce a mutation-aware Test-Driven Development workflow with mandatory 100% coverage verification.

28|5|Updated Oct 8, 2024
One-click install
npx skills add https://github.com/kabirnayeem99/Ktor2Curl --skill tdd-kabirnayeem99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/kabirnayeem99/Ktor2Curl/tree/main/.agents/skills/tdd
Command: npx skills add https://github.com/kabirnayeem99/Ktor2Curl --skill tdd-kabirnayeem99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of inconsistent code quality and fragile test suites by enforcing a rigorous, mutation-aware Test-Driven Development workflow that ensures every line of production code is verified by a failing test.

Core Features & Use Cases

  • Mutation-Aware Testing: Validates test effectiveness by ensuring tests actually catch bugs (mutants) rather than just providing false confidence.
  • Standardized Workflow: Provides a clear, non-negotiable cycle for feature development, bug fixes, and refactoring.
  • Coverage Verification: Enforces strict 100% coverage requirements with a clear process for handling exceptions and avoiding coverage theater.

Quick Start

Initiate the tdd skill to begin the development cycle for your new feature by writing a failing test that describes the expected behavior.

Frequently Asked Questions about tdd

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

FAQPage Schema
How does mutation testing improve test-driven development?

Mutation testing improves test-driven development by verifying that existing tests actually catch injected code defects, ensuring your test suite provides real quality assurance rather than false confidence from just passing.

What is the RED-GREEN-MUTATE-KILL-REFACTOR cycle in software development?

The RED-GREEN-MUTATE-KILL-REFACTOR cycle is a rigorous test-driven development workflow where you write a failing test, make it pass, inject mutants, kill them with tests, and then refactor the code.

How do I enforce 100% test coverage during refactoring?

To enforce 100% test coverage during refactoring, apply a standardized test-driven development workflow that mandates strict coverage verification for all production code changes and requires killing injected mutants.

Can I use this test-driven development workflow for bug fixes and new features?

Yes, you can use this test-driven development workflow for bug fixes and new features. It applies to all production code changes by enforcing a non-negotiable mutation-aware testing cycle to ensure quality.

How do I start a new feature using test-driven development?

To start a new feature using test-driven development, initiate the development cycle by writing a failing test that describes the expected behavior, then proceed through the mutation and refactoring stages to verify code quality.

Why does my test suite pass but still allow code regressions?

Your test suite passes but allows regressions because it lacks mutation testing effectiveness. Without verifying that tests can kill injected mutants, the suite may provide false confidence and fail to catch actual bugs.