Review test coverage

Use this prompt to review supplied tests against supplied feature, behavior, requirement, or implementation evidence and identify coverage quality, weak assertions, missing scenarios, and missing evidence.

  • Outcome
    Coverage review by feature
    Maps supplied features, behaviors, requirements, or implementation areas to matching tests, assertion quality, coverage status, and missing scenario gaps.
  • Use case
    Existing test evidence review
    Use when you have supplied tests and want to know whether they adequately cover supplied behavior, requirements, or implementation evidence.
  • Output
    Feature-level coverage schema
    Returns coverage status by feature, test quality findings, missing test scenarios by feature, missing evidence, and confidence.

Scope and best-fit use

Use this prompt to audit supplied test evidence against supplied behavior, requirements, or implementation evidence. It identifies coverage gaps but does not generate tests, write code, create patches, or produce a remediation plan.

You need to review existing test coverage

Use when supplied tests must be checked against supplied features, behaviors, requirements, implementation excerpts, assertions, fixtures, mocks, setup, cleanup, or coverage output.

  • Primary focus
    Coverage quality from supplied evidence
    Review what supplied tests cover, what they assert, whether assertions verify observable outcomes, and where supplied behavior is uncovered or weakly covered.
  • Gap identification
    Missing scenarios as coverage gaps
    Identify missing test scenarios by feature as review findings only. Do not write test cases, fixtures, mocks, code, or implementation steps.
  • Use another workflow when
    The task is regression risk, generation, patching, or planning
    Use a separate workflow for broader regression-risk analysis, test generation, code writing, patch creation, or changeset planning.

Inputs required

Provide the feature, behavior, requirement, or implementation evidence and the existing tests to review. Optional fixtures, mocks, setup, cleanup, logs, execution results, or coverage output may support the review, but the prompt must not invent missing evidence.

  • Test basis: The supplied feature, behavior, requirement, or implementation evidence that defines the expected behavior to review against.
  • Existing tests: The supplied test files, test excerpts, assertions, fixtures, mocks, setup, cleanup, and test data that should be reviewed.

Copy-ready prompt

Copy the prompt and replace the MATERIALS block with the supplied test basis, existing tests, and any optional supporting evidence. 

Run a test coverage review for the supplied materials.

TASK:
Audit supplied tests against supplied feature, behavior, requirement, or implementation evidence.

For each supplied feature, behavior, requirement, or implementation area:
- identify the expected behavior from the supplied materials
- identify matching existing tests
- determine what the tests assert
- classify coverage quality
- identify missing test scenarios as coverage gaps
- mark missing evidence where the supplied materials are insufficient

SCOPE:
Review supplied test evidence only.
Use supplied feature, behavior, requirement, or implementation evidence as the test basis.
Do not generate tests or produce a remediation plan.

EVIDENCE RULES:
Base findings only on the supplied materials.
Do not invent requirements, expected behavior, tests, assertions, fixtures, mocks, logs, coverage numbers, execution results, defects, or pass/fail status.
If a feature, behavior, requirement, implementation area, or matching test cannot be assessed from the supplied materials, mark it INSUFFICIENT_EVIDENCE.

COVERAGE QUALITY LABELS:
- Covered: supplied tests directly exercise the expected behavior and include meaningful assertions for the expected result.
- Weakly covered: supplied tests touch the behavior but assertions, setup, inputs, edge cases, or expected-result checks are incomplete.
- Not covered: no supplied matching test evidence covers the expected behavior.
- Not assessable: supplied materials are insufficient to determine coverage.

CHECK:
- expected behavior
- matching tests
- assertions and expected results
- positive paths
- negative paths
- edge and boundary cases
- error paths
- authorization or permission behavior, when relevant
- integration behavior, when relevant
- fixtures, mocks, setup, cleanup, and test data
- supplied coverage output, only if provided

OUTPUT:
A) Coverage status by feature
For each supplied feature, behavior, requirement, or implementation area:
- expected behavior
- matching tests
- assertion summary
- coverage quality: Covered / Weakly covered / Not covered / Not assessable
- evidence basis
- missing scenario gaps

B) Test quality findings
- weak assertions
- missing expected-result checks
- fixture, mock, setup, cleanup, or test-data issues
- overbroad or non-specific tests
- tests that execute behavior without verifying observable outcomes

C) Missing test scenarios by feature
List missing scenarios only as coverage gaps.
Do not write test cases, code, fixtures, mocks, or implementation steps.

D) Missing evidence
List the exact missing material needed to complete the review.

E) Confidence
State High / Medium / Low and explain the evidence basis.

OUT OF SCOPE:
- writing or modifying test code
- creating patches or implementation changes
- producing a remediation or changeset plan
- analyzing broader regression risk beyond the supplied test-coverage evidence
- claiming coverage, execution results, defects, or pass/fail status that are not supported by the supplied materials

MATERIALS:
"""
Replace this block with:
- feature, behavior, requirement, or implementation evidence
- existing tests
- assertions
- fixtures, mocks, setup, cleanup, and test data, if available
- coverage output, only if available
- logs or execution results, only if available
"""

Next steps

Use these related assets when the task needs code-quality review, refactor planning, or stricter evidence control.