skills.rest
OutlineDriven
OutlineDrivenOFFICIAL
Explore all skills by this author →
GitHub

test-driven

Define and apply test-driven development practices across programming languages.

5|2|Updated Nov 17, 2025
Search Tags:#testing#tdd#red-green-refactor#test-driven-development#mutation-testing#xp#property-based-testing
One-click install
npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill test-driven-outlinedriven
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-driven
Source: https://github.com/OutlineDriven/odin-gemini-cli-extension/tree/main/skills/test-driven
Command: npx skills add https://github.com/OutlineDriven/odin-gemini-cli-extension --skill test-driven-outlinedriven

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Tests define the specification. Design them from requirements before any implementation. The RED-GREEN-REFACTOR cycle keeps development focused on failing tests first, ensuring code only behaves as required and remains maintainable.

Core Features & Use Cases

  • Test-First Design: Write tests before code to capture requirements and prevent regressions.
  • RED-GREEN-REFACTOR Workflow: Iterative cycles that drive implementation, verification, and cleanup.
  • Guided by Frameworks: Leverages language-specific runners, property testing, and mutation tools to ensure robust coverage.

Quick Start

Begin by writing a failing test, then implement the minimal code to pass it, and finally refactor while keeping the tests green.

Frequently Asked Questions about test-driven

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

FAQPage Schema
What is test-driven development and how does the red-green-refactor cycle work?▼

Test-driven development (TDD) is a test-first design practice where you write a failing test, implement minimal code to pass it, and then refactor. This red-green-refactor cycle keeps development focused on expected outcomes and maintainable software.

How do I start writing tests before code to capture software requirements?▼

Begin by writing a failing test that defines your expected outcomes based on requirements. Then implement the minimal code required to turn the test green, and finally refactor the implementation while ensuring the tests stay green.

How does property-based testing fit into test-driven development practices?▼

Property-based testing supplements TDD by verifying code against generalized properties rather than specific examples. It leverages language-specific runners to generate varied test cases, ensuring robust coverage and measurable software quality.

Can I use test-driven development workflows for both bug fixes and refactoring?▼

Yes, test-driven development applies to feature development, bug fixes, and refactoring. It emphasizes writing tests first to prevent regressions, documenting workflows, and using mutation testing to verify code only behaves as required.

What is mutation testing and why use it in a test-first workflow?▼

Mutation testing is a technique to measure test suite effectiveness by modifying code and checking if tests fail. In a test-first workflow, it ensures your tests actually verify the implementation and provides measurable quality assurance.

Related Skills

Explore More Software Engineering Skills→
devantler-techdevantler-tech
3

test-driven-development

Enforce a test-first workflow with failing automated tests before implementation.

Official
Intermediate
DatTran26DatTran26

ck:test

Execute unit, integration, e2e, and UI tests with coverage reports.

Community
Advanced
yellow-seedyellow-seed

test-driven-development

Guide Red-Green-Refactor cycles for test-driven development workflows.

Community
Basic
TheBushidoCollectiveTheBushidoCollective
187

bdd-principles

Conduct Three Amigos sessions and produce executable scenarios for BDD workflows.

Official
Intermediate