test-gap-analysis

Test gap analysis identifies weak tests by reasoning about hypothetical mutations—such as boundary, logic, and null handling changes—that could alter behavior without being detected by your current .NET test suite, producing prioritized recommendations with concrete fixes.

Pseudo-mutation reasoning approximates mutation testing statically through review-style analysis, evaluating how hypothetical code changes affecting boolean logic or exception handling might survive your tests, classifying mutations into killed, survived, no-coverage, or equivalent categories.

Yes, test gap analysis works with xUnit, NUnit, MSTest, and TUnit, evaluating test effectiveness across these common .NET frameworks to identify gaps where boundary, arithmetic, or exception-handling bugs might escape detection.

You can analyze test coverage gaps without runtime mutation tools by applying static gap analysis during code review, pairing production code with corresponding tests to reason through hypothetical mutations and identify where coverage looks good but tests miss real defects.

Use static test gap analysis during code review or test hardening planning when you need to prioritize test improvements quickly, approximating mutation testing through reasoning while avoiding the runtime execution overhead of traditional mutation testing tools.

To perform test gap analysis, you need to provide your production files and their corresponding test files, allowing the Skill to classify mutations and return prioritized recommendations for gaps where tests would likely not catch bugs.