Radberi-TDD

Guide test-driven development workflows in C# with Red-Green-Refactor cycles.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/primeBeri/huml-dotnet --skill radberi-tdd-primeberi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Radberi-TDD
Source: https://github.com/primeBeri/huml-dotnet/tree/main/.claude/skills/Radberi-TDD
Command: npx skills add https://github.com/primeBeri/huml-dotnet --skill radberi-tdd-primeberi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill guides developers in adopting test-driven development practices to ensure code correctness and maintainability from the outset.

Core Features & Use Cases

  • Fosters TDD discipline: Provides detailed principles and workflows for writing failing tests first, then minimal code, and refactoring.
  • Guides best practices: Emphasizes naming conventions, test structure, and avoiding anti-patterns to improve software quality.
  • Use Case: A developer adopts TDD in a new C# project, writing a failing test for a feature, then implementing just enough code to pass, iterating until the feature is complete with robust tests.

Quick Start

Implement a failing test that verifies a function throws an exception for invalid input, then write the minimal code to make it pass, following the Red-Green-Refactor cycle.

Frequently Asked Questions about Radberi-TDD

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

FAQPage Schema
How do I practice test-driven development in C# to improve code correctness?

Test-driven development in C# involves writing a failing test first, implementing minimal code to pass it, and refactoring. This Skill provides detailed principles and workflows to maintain discipline and improve software quality.

What are the best practices for structuring xUnit tests in .NET?

Best practices for xUnit tests include following clear naming conventions, maintaining structured test organization, and avoiding anti-patterns. This Skill guides developers in writing effective, meaningful tests for robust software.

Can I use this TDD workflow for an existing C# project, or is it only for new code?

The TDD workflow detailed here is ideal for new C# projects, though the principles and best practices for writing failing tests first and refactoring apply equally to maintaining and extending existing software.

What is the Red-Green-Refactor cycle in test-driven development?

The Red-Green-Refactor cycle in test-driven development means writing a failing test, creating minimal code to make it pass, and then refactoring. This Skill encourages this systematic approach for feature iteration.

Why should I write a failing test before implementing the feature logic?

Writing a failing test first ensures code correctness and maintainability from the outset. This Skill fosters TDD discipline by verifying a function throws exceptions for invalid input before any logic is implemented.

How do I avoid anti-patterns when writing tests for .NET applications?

Avoiding anti-patterns in .NET tests requires emphasizing clear naming conventions and structured test design. This Skill provides comprehensive guidelines to improve developer discipline and software quality.