devbooks-test-reviewer

To review test suite coverage without modifying code, perform a non-execution assessment of the tests/ directory. This evaluates coverage, boundary condition handling, readability, and maintainability while keeping the source code completely intact.

A non-execution test review evaluates test suites by statically analyzing coverage, boundary checks, and readability rather than executing them. It produces a structured Test Review Report documenting gaps and recommendations without relying on actual test execution outcomes.

You can map acceptance criteria to test cases during a code review by reading the verification.md file to align project standards with the tests/ directory. This ensures the test suite accurately reflects and verifies the required acceptance criteria.

Yes, static test review supports role-based constraint checks by enforcing strict conformance to CON-ROLE-001 through CON-ROLE-005. It provides structured escalation paths when issues or constraint violations are found during the assessment.

Yes, you can evaluate test maintainability and readability for existing test suites through a formal non-execution assessment. The review identifies specific readability improvements and maintainability gaps while generating a comprehensive Test Review Report.

The main limitation of non-execution test reviews is that they rely on static assessments rather than actual test outcomes. This means they cannot verify runtime behavior or execution failures, focusing solely on structural coverage, boundary checks, and documentation gaps.