Software Development
Code Testing
ALWAYS USE for test work that requires changes: write, add, generate, repair, or strengthen tests for existing code in xUnit, MSTest, NUnit, pytest, Vitest/Jest, Go, or another framework. Includes regression cases, failing or flaky tests, coverage-driven additions, and audit-then-fix requests. Focused work stays direct; broad or multi-stage work invokes test-engineer. DO NOT USE for only running tests, analysis-only audits, framework/platform migrations, a test blocked on a missing production seam (testability-obstacle), or MSTest API/configuration corrections that do not design new cases (writing-mstest-tests). Within an active test-engineer pipeline, reuse supplied guidance and do not re-enter this skill.
- Publisher / source
- dotnet/skills (found on skills.sh)
- Upstream record
- dotnet/skills
- Version
- Version 1
- Published
- Publication review
- Approved for publication · recorded passed scan 2026-11-01
- Content fingerprint
1a6adfcfe2d3be48c7ad2a72b1d1bd09991cfe5f5273708e58c88e84865fb332