What is the Red phase in TDD?

The Red phase is the first step of Test-Driven Development where you write a test that fails before writing any implementation code to define the expected behavior.

Does this skill run the tests automatically?

It provides commands to trigger tests via a TDD enforcer script, helping you verify that tests fail for the correct reasons before proceeding to the Green phase.

Why is the Red phase important?

It ensures your tests are actually testing the intended logic and prevents 'false positives' where tests pass accidentally without the feature being implemented.

Which programming languages does this skill support?

It includes specific patterns and file naming conventions for Python, Go, TypeScript, and Rust, but the principles apply to any language.

How does this skill help with test naming?

It enforces a descriptive naming convention (test_function_scenario_expected) to ensure clarity and documentation within your test suite.

TDD Red Phase Assistant

Name: TDD Red Phase Assistant
Author: pagerguild

bypagerguild

보안 및 테스팅

Guides developers through the initial phase of Test-Driven Development by designing and validating failing tests before implementation.

소개

This skill automates and enforces the 'Red' phase of the Test-Driven Development (TDD) cycle within Claude Code. It provides domain-specific guidance on writing descriptive, behavior-focused test cases using the Arrange-Act-Assert (AAA) pattern across multiple languages like Python, Go, and TypeScript. By facilitating the creation of tests that fail for the correct reasons, it ensures robust code design and prevents trivial passes, helping developers maintain high code quality and test coverage from the very start of a feature's lifecycle.

주요 기능

Enforces Test-First development patterns across major languages
Identifies common TDD pitfalls like trivial or vague tests
0 GitHub stars
Guides Arrange-Act-Assert (AAA) test structure implementation
Automates TDD phase management via CLI integration
Standardizes naming conventions for clear test scenarios

사용 사례

Onboarding developers to standardized TDD workflows and naming conventions
Starting a new feature development with a strict test-first approach
Designing edge-case assertions and scenarios before writing business logic

소개

주요 기능

Enforces Test-First development patterns across major languages
Identifies common TDD pitfalls like trivial or vague tests
0 GitHub stars
Guides Arrange-Act-Assert (AAA) test structure implementation
Automates TDD phase management via CLI integration
Standardizes naming conventions for clear test scenarios

사용 사례

Onboarding developers to standardized TDD workflows and naming conventions
Starting a new feature development with a strict test-first approach
Designing edge-case assertions and scenarios before writing business logic