dotnet-test

Use the writing-mstest-tests sub-skill to create tests following MSTest conventions, including correct AreEqual argument order, Assert.Throws instead of ExpectedException, and DynamicData patterns. Tests should follow the strict TDD red-green cycle defined by the strict-tdd skill.

Use find-untested-sources to list production files and classes without test coverage, or test-gap-analysis for pseudo-mutation analysis that finds behaviors no test covers. Combine with coverage-analysis and crap-score to prioritize what to test first.

CRAP score combines cyclomatic complexity with lack of coverage to rank risky code. The crap-score sub-skill calculates it so you can prioritize testing complex, uncovered methods before simpler ones.

The generate-testability-wrappers and migrate-static-to-wrapper sub-skills create injectable wrappers for static dependencies. However, in architectures without dependency injection this requires explicit user approval due to its architectural impact.

Tests that never fail are a common anti-pattern detected by the test-anti-patterns sub-skill, along with asserts without messages, order dependencies, and shared state. The assertion-quality sub-skill also flags generic Assert.IsTrue calls that should use specific assertions.