domains / families / software-engineering / code-testing

code-testing

separate

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.

When to use

• Generate unit tests for an entire project or specific files
• Improve test coverage for existing codebases
• Create test files that follow project conventions
• Write tests that actually compile and pass
• Add tests for new features or untested code
• Generate or extend MSTest suites; load `writing-mstest-tests` as supporting

When not to use

• Running or executing existing tests (use the `run-tests` skill)
• Migrating between test frameworks (use migration skills)
• Answering an MSTest API/pattern or modernization question that does not ask to
• Analysis-only diagnosis of failing tests when no code or test changes are

Skill page

Source