test-anti-patterns

Test anti-patterns in .NET are detected by scanning test files for missing assertions, flaky timing, and over-mocking. The scan generates a structured report with severity levels, file locations, and recommended fixes for each finding.

Common code smells in xUnit, MSTest, and NUnit tests include missing assertions, poor test isolation, inadequate naming, flakiness indicators, and excessive mocking. Identifying these issues helps improve test reliability, maintainability, and diagnostic value.

Yes, TUnit test files can be scanned for flakiness indicators alongside MSTest, xUnit, and NUnit suites. The scan evaluates timing issues and isolation problems, generating a prioritized set of improvements with concrete remediation guidance.

The best way to audit .NET tests for over-mocking and assertion quality is to perform an automated scan across multiple test files. This produces severity-labeled findings with specific file locations and actionable fixes to improve overall test quality.

No, the test anti-pattern scan requires no external dependencies or components to function. It directly analyzes your provided .NET test code to identify and report structural issues and code smells.