skills.rest
aggutierrez98
aggutierrez98COMMUNITY
Explore all skills by this author →
WebsiteGitHub

strict-tdd

Enforces a red-green TDD cycle for behavior changes in C# service and data layers.

Updated Aug 24, 2026
Search Tags:#tdd#csharp#integration testing#unit testing#test runner#red-green#mstest
One-click install
npx skills add https://github.com/aggutierrez98/TP-TD --skill strict-tdd-aggutierrez98
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: strict-tdd
Source: https://github.com/aggutierrez98/TP-TD/tree/main/.agents/skills/strict-tdd
Command: npx skills add https://github.com/aggutierrez98/TP-TD --skill strict-tdd-aggutierrez98

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It prevents untested behavior changes in a C# codebase by requiring a failing test to be written and observed before any implementation, eliminating after-the-fact tests presented as TDD. ## Core Features & Use Cases - Strict red-green workflow: Verify a green baseline, write the failing test first, observe the red via the test runner, implement the minimal change, then confirm green with exit code 0. - Scoped test project routing: Directs unit tests to SERVICIOS.Tests and BLL.Tests, and integration/regression tests to TpIDS.IntegrationTests run with the -IncludeIntegration flag. - Forbidden pattern enforcement: Blocks implementing before testing, declaring unobserved failures, weakening tests to force green, and substituting FlaUI UI tests for the unit/integration cycle. - Use Case: When fixing a bug in BLL permission logic, write a failing Metodo_Escenario_Resultado test that reproduces the bug, watch it fail with run-tests.ps1, then implement the fix and confirm the suite passes. ## Quick Start Use the strict-tdd skill to add a new validation rule to the BLL layer by writing the failing test first and following the red-green cycle.

Frequently Asked Questions about strict-tdd

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

FAQPage Schema
How do I practice strict TDD in a C# MSTest project?▼

Write the failing test first using the Metodo_Escenario_Resultado naming convention, run the test runner to observe the failure, then implement the minimal change and rerun until exit code 0. Never implement before the test exists and fails.

What is the red-green TDD cycle for unit and integration tests?▼

Red-green TDD means writing a test that fails (red), implementing the minimum code to pass it (green), then refactoring with the suite green. A green baseline must be confirmed before writing the new test.

Does a compilation error count as a failing test in TDD?▼

A build error only counts as red if the test deliberately expresses an API or seam that does not exist yet. In that case the runner stops at build with no TRX, so you implement the minimal seam until you get an assertion-level failure.

When should UI tests be written in a TDD workflow?▼

FlaUI UI tests are written or updated after development completes, never as part of the red-green cycle. The unit and integration test cycle drives behavior changes; UI tests only cover end-to-end flows afterward.

When does strict TDD not apply to code changes?▼

It does not apply to purely visual WinForms or .Designer.cs changes, documentation, scripts, or behavior-preserving refactors. For pure refactors, existing tests must stay green but no new test is required.

Related Skills

Explore More Software Engineering Skills→
jacobrocks1212jacobrocks1212

mstest

Filter MSTest results to show pass/fail and errors in .NET projects.

Community
Intermediate
KibertumKibertum
16

ship

Automate task review, testing, and commit for repository closure.

Official
Advanced
nanorepublicananorepublica
61

Testing Unit Tests

Standardize unit-test coding practices across Claude Code projects.

Community
Basic
erenisiklarerenisiklar

test-driven-development

Enforce a test-driven development workflow with the RED-GREEN-REFACTOR cycle.

Community
Advanced