Review test cases and coverage gaps. Use when analyzing unit tests, integration tests, missing test files, stub-only specs, uncovered edge cases, untested error paths, missing Spring Boot @WebMvcTest or @SpringBootTest controllers, unmocked external API calls, or Angular component specs that only contain the auto-generated should create assertion.
Apply this skill to audit how thoroughly the backend and frontend are tested. Focus on gaps, not on writing new tests.
backend/src/main/java/ and find its counterpart in backend/src/test/java/. Flag missing test classes..ts source file in frontend/src/app/ and check for a .spec.ts counterpart. Flag missing specs.| Severity | file/path | description of issue | concrete suggestion || Severity | Meaning |
|---|---|
| High | Critical service, controller, or guard has zero test coverage |
| Medium | Test file exists but contains only auto-generated stub, or error paths not tested |
| Low | Minor coverage gap for non-critical utility or simple DTO |
Backend:
*Service.java with no *ServiceTest.java counterpart*Controller.java with no @WebMvcTest or @SpringBootTest test@Transactional methods with no rollback/error path testFrontend:
*.ts component with no *.spec.ts file at allit('should create', () => { expect(component).toBeTruthy(); })HttpClientTestingModule