test-fix

To fix test gaps from a test audit report, use an audit-driven tool that reads documented gaps like MISSING_TEST or MISSING_FIXTURES and applies targeted test modifications only to those specific areas, preserving existing tests without rebuilding everything.

Audit-driven test gap analysis reads test-audit reports to identify specific coverage gaps such as MISSING_TEST, MISSING_FIXTURES, and MISSING_METHOD across domain and application layers, then updates or adds tests exclusively for those documented gaps.

Yes, an existing test-audit report located in the claudedocs directory is required before applying audit-driven test fixes. The tool reads these reports to identify exact gap types and locations rather than scanning the codebase independently.

Yes, targeted test fixes preserve existing tests and fixtures unless a specific documented gap requires changes. The tool applies non-destructive updates by modifying or adding tests only where gaps like MISSING_FIXTURES are explicitly reported in the audit.

The best way to refactor tests for specific domain layer gaps is to use an audit-driven test fix approach that reads gap reports and applies targeted updates such as adding MISSING_TEST or MISSING_METHOD tests for the specified domain layer only.

Existing tests and fixtures are preserved during audit-driven test fixes unless a reported gap explicitly requires changes. The tool focuses on non-destructive updates, modifying only areas identified by gap types like MISSING_TEST or MISSING_METHOD in the audit report.