Can this skill help reduce technical debt?

By enforcing meaningful tests and design principles like SOLID and DRY during the Refactor phase, the skill helps prevent the accumulation of messy or unmaintainable code.

How does the skill handle mock objects?

It provides clear definitions and implementation patterns for various test doubles, including Dummies, Stubs, Spies, Mocks, and Fakes, helping you choose the right one for your scenario.

What is the Red-Green-Refactor cycle in this skill?

It is a three-step TDD process: 'Red' involves writing a failing test, 'Green' focuses on writing the minimal code to pass that test, and 'Refactor' involves cleaning up the code while keeping the test passing.

Does this skill support specific .NET testing frameworks?

Yes, it is designed to work with popular frameworks like xUnit, NUnit, and MSTest, providing patterns like AAA that are universal across the .NET ecosystem.

.NET TDD Workflow

Name: .NET TDD Workflow
Author: DoubleslashSE

byDoubleslashSE

•

Security & Testing

Guides the Red-Green-Refactor development cycle for .NET applications to ensure robust, testable, and maintainable code.

About

The .NET TDD Workflow skill provides Claude with a comprehensive framework for implementing Test-Driven Development within the .NET ecosystem. It enforces the essential Red-Green-Refactor cycle, ensuring that tests are written before implementation and that code remains clean through structured refactoring. The skill includes built-in guidance for the AAA (Arrange-Act-Assert) pattern, standardized naming conventions, and the appropriate application of test doubles like mocks, stubs, and fakes. By utilizing this skill, developers can reduce technical debt and improve software quality by following industry-standard testing patterns and avoiding common 'test smells.'

Key Features

AAA (Arrange-Act-Assert) pattern enforcement
Guided Red-Green-Refactor workflow specifically for .NET
Standardized test naming conventions (Method_Scenario_Expected)
1 GitHub stars
Anti-pattern detection to prevent brittle or redundant tests
Comprehensive guidance on using Mocks, Stubs, and Spies

Use Cases

Creating a robust suite of unit and integration tests for web APIs
Developing new .NET features with a test-first methodology
Safely refactoring legacy C# codebases while maintaining functional parity

About

Key Features

AAA (Arrange-Act-Assert) pattern enforcement
Guided Red-Green-Refactor workflow specifically for .NET
Standardized test naming conventions (Method_Scenario_Expected)
1 GitHub stars
Anti-pattern detection to prevent brittle or redundant tests
Comprehensive guidance on using Mocks, Stubs, and Spies

Use Cases

Creating a robust suite of unit and integration tests for web APIs
Developing new .NET features with a test-first methodology
Safely refactoring legacy C# codebases while maintaining functional parity