Test Case and Requirement Reviews

The review workflow in BesTest brings the same rigor to test quality that code review brings to code. A new test case starts in Draft. When it is ready, the author sends it to review: pick one or more reviewers, add a note about what to check, and set a due date. Reviewers are notified, and BesTest shows who the item is still waiting on. Each reviewer approves or requests changes, with comments; once approved, the test case becomes Active and ready for execution.

Requirements use the same workflow. Send a requirement for review before test cases are written against it, so the business and functional need is signed off first - Draft, In Review, Approved, with Changes Requested when a reviewer wants edits. The requirement's stats bar shows its approval state at a glance.

Reviews catch problems while they are cheap: ambiguous steps different testers would read differently, missing test data, expected results that no longer match the specification, and duplicates of existing coverage. That matters more as AI agents start drafting test cases - a human still decides whether each one is true.

Consecutive submissions are grouped into Review Cycles, so the review audit trail shows who was asked, who answered, what changed and how many rounds it took. For teams in regulated industries this is the evidence that testing was planned with diligence. Admins decide per project whether review is Required, Optional or Off; when it is not Required, a test case can be set to Active directly.