Skip to main content
Version: 1.0.8

Review Workflow

Every AI-generated test case passes through a review gate before it can reach the main test repository.

The Three Statuses​

StatusBadgeMeaning
PENDING_REVIEWPending ReviewThe default for a newly generated case. Nobody has decided yet.
APPROVEDApprovedA reviewer accepted the case. It can be saved to the repository.
REJECTEDRejectedA reviewer turned the case down. It stays in the session for reference but cannot be exported.

Cases arrive as Pending Review. Regenerated cases and duplicates are reset to Pending Review as well — an approval never carries over to a new version.

The Three Actions​

ActionWhat it does
ApproveMoves the case to Approved and makes it eligible for repository export
RejectMoves the case to Rejected
Reopen / Re-reviewSends an approved or rejected case back to Pending Review

Approve runs immediately, without a dialog, so a long review pass is not interrupted. Reject and Reopen open a dialog with an optional Comment field, up to 1,000 characters, which is stored in the review history.

Where You Review​

In an AI Session​

The generated results list is the main review surface.

  • Each row carries its review status in the Status column, and the badge is itself a dropdown.
  • The column's filter narrows the list to Pending Review, Approved, or Rejected.
  • Opening a row's status badge lists the three statuses — Pending Review, Approved, Rejected — plus View history. Picking a status other than the current one applies it; the current one is disabled.
  • Selecting several rows brings up the selection bar with bulk Approve and Reject.

Bulk approve and bulk reject take an optional shared comment. There is no bulk reopen — reopen always acts on a single case.

In the Test Repository​

Repository test cases carry the same badge.

The case detail pane's overflow menu offers Approve, Reject, and Re-review, and the tree's right-click menu offers the same three actions on a node.

The Approved state is rendered quietly, because it is the normal state for a repository case; the badge is there to draw attention to Pending Review and Rejected.

Review History​

Review History opens a chronological timeline for one test case.

Each entry shows:

  • The action taken (Approved, Rejected, or Pending Review)
  • Who took it
  • When
  • The comment, if one was left

The dialog also states the case's current status. A case with no entries reads "No review actions yet — this case is still pending."

The Export Gate​

This is the reason the workflow exists: only approved cases can be saved to the main test repository.

When you select cases and press Save to Repository, one of three things happens.

Your selectionWhat happens
Nothing approvedThe button is disabled, with a note that only approved test cases can be saved
Partly approvedA dialog offers to continue with just the approved subset, and counts the approved, rejected, and pending cases in the selection
Fully approvedThe export dialog opens directly

Choosing Save N Approved narrows the selection to the approved cases and continues.

Permissions​

Review actions are gated on the casewriter:review:update permission.

  • Without it, the approve, reject, and reopen controls are not rendered.
  • The regeneration comparison dialog becomes view-only, since accepting or declining a regenerated case is also a review action.
  • If a request is rejected by the server, the interface says which permission is required rather than naming a role.

Suggested Team Process​

  1. Run a generation session.
  2. Filter the results to Pending Review.
  3. Read each case; fix small problems with Edit, and send weak ones back through Regenerate.
  4. Approve what is good and Reject what is not, leaving a comment when the reason is not obvious.
  5. Select the approved cases and Save to Repository, choosing the target test set.
  6. Use Review History when someone asks why a case was accepted or turned down.