refactor-tests

Test files exceeding 500 lines often indicate a need for splitting. Analyzing these large files helps detect mixed responsibilities where one test covers multiple modules or concerns, and flags manual mock objects that should be replaced with standard mocking libraries to improve overall maintainability.

To split test files with mixed responsibilities, analyze the code to pinpoint tests covering multiple modules or concerns. By detecting these mixed responsibilities, you can separate the tests into distinct, focused files that each target a single module, improving readability and maintainability.

The best way to analyze a test suite for code quality issues is to collect the test files, prioritize those exceeding 500 lines, and analyze them sequentially. This approach detects large file sizes, mixed responsibilities, and manual mocking to suggest ideal refactoring states.

Yes, you can detect manual mock objects in your tests by analyzing the test files for hardcoded mock implementations. This analysis flags instances where standard mocking libraries should be used instead, helping to improve test code quality and maintainability.