test-coverage-improver

To find low test coverage gaps in a node-redis monorepo, execute per-package nyc coverage runs and parse the coverage artifacts. This analysis identifies low-coverage files, branches, and risky error handling code paths across client, cluster, and module packages.

Generate mocha tests for uncovered node-redis code paths by prioritizing high-coverage gaps and designing targeted test scenarios for error handling and edge cases. Proposed tests are presented for user approval before implementation and validation against repo lint and build standards.

Yes, you can analyze test coverage for individual packages in a JavaScript monorepo by running per-package nyc test suites. This isolates coverage artifacts for specific client, cluster, or module packages to accurately identify uncovered branches and risky logic.

The best way to improve test coverage for Redis client error handling is to parse nyc coverage artifacts to locate risky uncovered code paths, then generate high-impact mocha test proposals targeting those specific error handling scenarios.

No, the test coverage improvement process uses user-coordinated implementation where it automatically designs and proposes targeted tests with expected coverage gains. After user approval, it writes the tests and validates them via coverage reruns and lint checks.

If nyc coverage runs are not reflecting new test improvements, validate updates by executing coverage reruns and lint checks after implementing approved tests. Ensuring tests align with repo standards prevents build failures that block coverage artifact generation.