skills.rest
andredosreis
andredosreisCOMMUNITY
Explore all skills by this author →
GitHub

tdd

Implement test-driven development using the red-green-refactor cycle.

Updated Aug 27, 2026
Search Tags:#tdd#coding standards#test-driven development#red-green-refactor#development practices
One-click install
npx skills add https://github.com/andredosreis/laura-saas-agenda --skill tdd-andredosreis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/andredosreis/laura-saas-agenda/tree/main/.gemini/skills/tdd
Command: npx skills add https://github.com/andredosreis/laura-saas-agenda --skill tdd-andredosreis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill aids in implementing Test-Driven Development (TDD) practices, helping users write tests before code, and refactor effectively.

Core Features & Use Cases

  • Test-Driven Development: Encourages writing tests first, then implementing code that passes those tests.
  • Red-Green-Refactor Loop: Follows a cycle of writing a failing test (RED), making it pass (GREEN), and then refactoring (REFACTOR).
  • Use Case: Ideal for developers who want to integrate TDD into their workflow, especially when working on complex features or fixing bugs.

Quick Start

Use the tdd skill to initiate a TDD session for your new feature by writing a test for the expected behavior.

Frequently Asked Questions about tdd

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 is a coding practice where you write a failing test (RED), implement code to pass it (GREEN), and then refactor cleanly. This cycle ensures features are built around expected behavior and test coverage from the start.

How do I start writing tests before code for a new feature?▼

To start writing tests before code, initiate a test-driven development session by writing a test defining the expected behavior of your new feature. Run it to see it fail, then write the minimum code required to make it pass.

Do I need prior understanding of TDD principles to use this workflow?▼

Yes, you need a foundational understanding of test-driven development principles and practices. This workflow is designed for developers who already grasp the basics and want to actively integrate the red-green-refactor cycle into their coding.

When should I use test-driven development in my software engineering workflow?▼

Test-driven development is ideal when working on complex features or fixing bugs. It helps you enhance coding standards by ensuring every new behavior is validated by tests before implementation, reducing regressions in your workflow.

What is the best way to refactor code after passing a test?▼

The best way to refactor after passing a test is to clean up the code without changing its external behavior. This ensures the newly implemented feature remains functional while improving code quality and maintaining test coverage.

Related Skills

Explore More Software Engineering Skills→
webdriveriowebdriverio
11

Testing Test Writing

Guide test writing to adhere to coding standards.

Official
Basic
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
thktthkt
11

test

Execute project tests and analyze code coverage with package managers and linters.

Community
Intermediate
pyzepyze

bdd-scenarios

Convert specification examples into executable Given/When/Then scenarios using clojure.test.

Official
Basic