test-reviewing

To validate unit test quality and check London School pattern compliance, execute generated tests to verify mock configurations, confirm no I/O usage, and categorize failures into structural, mock, assertion, or runtime classes.

The best way to review mock configurations in unit tests is to validate that mocks use appropriate stubs, verify types match expected interfaces, and ensure dummy values are correctly configured before running specification verification.

You categorize unit test failures by executing the tests and classifying errors into structural, mock, assertion, or runtime categories, which directly guides the targeted fixing process for each failed test.

Yes, you can use automated test review as a quality gate between test generation and specification verification by executing tests, analyzing structural adherence, and validating mocks before proceeding to coverage checks.

Generated unit tests fail structure analysis when they violate London School pattern rules, such as improper mock usage, performing I/O operations, lacking isolation, or failing to meet naming conventions and spec tag requirements.

Yes, you need to generate unit tests before running an automated test review, because the review process executes the generated tests, analyzes their structure, and validates mock configurations to ensure robustness.