review-tests

To identify coverage gaps in tests for changed behavior, run a diff-driven review that analyzes touched test files and implementation code. This process evaluates behavioral coverage over simple line counts and outputs a structured assessment with actionable recommendations to fix missing edge cases.

Test brittleness refers to fragile tests with flaky mocks, brittle assertions, or over-constrained expectations that fail unpredictably. You detect test brittleness by evaluating test suites against changed behavior, which surfaces these structural weaknesses and provides recommendations to improve overall test quality.

Yes, this test review approach works across both frontend and backend codebases. It evaluates test suites touched by diffs or behavioral changes regardless of the stack, focusing on behavioral coverage, brittleness detection, and quality improvements for the changed implementation.

You need to run a behavioral test coverage analysis when test files or implementations under test change, specifically before pushing code. It is also recommended when seeking a test review to ensure new behavior is properly covered and existing tests are not brittle.

Review tests for missing edge cases by applying a diff-driven analysis to changed behavior. This method identifies gaps in coverage and brittleness across affected test suites, outputting a structured assessment with actionable recommendations to improve test quality before push.