⚠️Review is available in Business and Enterprise subscriptions.
Test case review works like a pull request for your test repository. An author submits a new or updated test case, one or more reviewers evaluate it, and only after approval can the changes be merged into the repository. This prevents untested, incomplete, or poorly structured cases from reaching your test runs.
Review is configured per project, so you can enforce it strictly in regulated projects while leaving it optional in exploratory ones.
Configuring review settings
Open Project Settings → General and configure the review options:
Setting | Effect |
Review enabled | Team members can optionally send test cases to review. |
Review is mandatory | All test case changes must go through review — the direct Save button is removed. |
Self merge | Allows the review author to merge their own changes (subject to approval requirements). |
Approvals required | Sets the number of approvals needed before a review can be merged. |
We recommend enabling mandatory review for any project where test cases drive compliance or release decisions. For fast-moving exploratory projects, optional review is usually enough.
The review workflow
Submitting for review
Create or edit a test case in the repository.
Instead of saving directly, select Send to Review.
The case appears in the Review section with a type label:
New case — a brand-new test case entering the repository.
Update — changes to an existing test case.
When review is mandatory, the Save button is replaced entirely — Send to Review is the only option.
Reviewing a submission
Open any review from the Review section to see a changelog of what was added or modified, along with comments from other reviewers.
Reviewer actions:
Action | Purpose |
Approve | Cast your vote in favor. The review is not merged yet — other reviewers may still need to weigh in. |
Request Changes | Signal that the case needs work. This is a status indicator visible to all reviewers and the author. |
Edit | Suggest modifications directly within the review. |
Merge | Accept the changes into the repository. Only available when all approval requirements are met. |
Decline | Reject the review entirely. |
Author actions:
Edit — revise the case based on feedback and resubmit.
Merge — available only when self-merge is enabled and required approvals are met (or no approval count is set).
Decline — withdraw the review.
Both authors and reviewers can leave comments throughout the process.
Merging
Once the required approvals are met, any authorized user can merge. For new cases, the test case appears in the repository. For updates, the reviewed changes replace the current version.
Note: If self-merge is enabled but an approval count is set, the author still cannot merge until the required number of approvals is reached.
Permissions
The ability to review, approve, and merge is governed by workspace roles. Ensure reviewers have the appropriate permissions in their role configuration. Owners and administrators can review by default; for custom roles, grant review permissions explicitly.
FAQ
Can I review test cases in bulk?
Reviews are submitted per test case. However, you can view and manage all pending reviews from the centralized Review section in each project.
What happens to a test case while it is in review?
The existing version (if any) remains unchanged in the repository and can still be included in test runs. The reviewed version only takes effect after merging.
Does review work with imported test cases?
Imported cases land directly in the repository. If you need them reviewed, edit them after import and send the update to review.