test-quality-check

To audit test quality, upload your *Tests.cs, *Spec.cs, and WebAppFactory.cs files. The assessment checks FluentAssertions usage, NSubstitute mocking patterns, and naming conventions to surface categorized quality gaps.

Common quality gaps include inconsistent naming conventions, missing edge-case coverage, and improper mocking isolation. The assessment identifies these issues across unit, integration, and architecture tests and classifies them by severity.

To enforce Given_When_Then naming conventions, upload your test files for analysis. The assessment scans MarketNest.UnitTests and related suites to identify deviations and provides actionable code fixes.

Yes, the test quality check supports architecture tests using NetArchTest. It audits MarketNest.ArchitectureTests to surface findings related to architectural rules and provides structured severity reports.

Yes, you can get actionable code fixes for integration test isolation. The assessment outputs categorized results with ready-to-apply scaffolds to address BLOCKER and HIGH severity isolation issues.

The best way to prioritize test suite maintenance findings is to use a structured report classifying issues as BLOCKER, HIGH, MEDIUM, or SUGGESTION. This provides a clear risk hierarchy for addressing quality gaps.