AI-Generated Test Review

Determine whether AI-generated tests prove real behavior instead of merely raising coverage or producing green builds.

When to Use

Reviewing, changing, or accepting AI-generated unit, functional, API, or E2E tests.
A test passes but its assertions, isolation, data, or coverage value is doubtful.

Inventory test types and files actually present in scope: unit, functional test, API, E2E, or a combination. Review only discovered or user-specified types.
Establish the behavior, risk, and available requirement or implementation evidence. Mark missing evidence; do not invent findings.
Read prompts/review-test.md and report actionable findings by severity, tied to a test, risk, and repair direction.
Load rules only for discovered layers: unit, functional test, API, or E2E. Load more than one only for cross-layer concerns; do not perform a global review just because multiple rule files exist.
Separate merge-blocking faults from improvements; do not call an effective test defective because of style preference.