Test case review

What is a review in a test case?

In Qase, it is possible to ensure that the test cases being created are first verified by someone superior, such as a QA team manager, supervisor, CTO, or other responsible parties.

Review is available in Business and Enterprise subscriptions.

Review configuration

In the project settings, you can define several options regarding test case review:

• Review enabled: If selected, you and your teammates will have the option to send a test case to review.

• Review is mandatory: If selected, any changes submitted for a test case cannot be updated unless it’s sent to review.

• Self Merge: This option permits the initiator of the review to merge the changes requested in the review.

• Approvals required: In order to merge the changes, the number of approvals (determined by the administrator/owner) will have to be met.

Example of submitting for a review

Let's go about creating a new test case and submitting it for review:

• Just like with a regular flow of creating test cases, navigate to the repository, and create a new case:

  
• Fill in all the necessary details, define steps, etc. Once ready, hit the "Send to Review" button at the bottom of the screen: In a scenario where a review is set to "Mandatory", there will be no option to "Save" or "Save and create another" - only send your test case to review:
• Once a test case has been sent to review, you will now find a new case review request under the "Review" section:

  
• If you create a new case and send it to review, it will be labeled as "New case". If you make changes to an existing test case and send it to review, it will be labeled as "Update".

• From the "Review" section, you can go into every particular review there is. In a review, you will find a changelog of a test case and comments that have been left regarding this review:

  
• For an author and a reviewer, available actions will be different - a reviewer will also be able to "Approve" or "Request changes"

• Both a review author and other reviewers can leave comments and see others' comments left before.

Merging a review

Once a review is approved (again, depending on the pre-defined requirements in project settings), a review can be merged. After that, a new test case will appear in the repository, or the reviewed updates will be set for an existing test case:

Step 1: Before review

Step 2: Merging review

Step 3: After merging review

Reviewers' and authors' abilities

For Reviewers:

If you are reviewing a test case that someone else submitted, you will see five options on the right side of the page: merge, approve, request changes, edit, and decline.

Clicking on Merge means you accept and update the test case with the suggested changes. By clicking Approve, you vote for the change, while other reviewers can still look at the suggested updates.

Clicking Request Changes updates your status as someone who has requested changes. This feature lets other reviewers know that you've requested changes.

Clicking Edit lets you suggest further changes to the review.

Clicking Decline allows you to decline the review request.

For Authors:

If you are the person who created the review, you can merge the review yourself if both of the following conditions are met:

1. Self-merge is enabled in the settings.

2. The required number of approvals is not set.

If these conditions are met, the author will see a page with three options: merge, edit, and decline.

Here’s what the page would look like if the conditions stated above were not met. You will have the option to edit and decline the review.

If you are the author and the self-review option is enabled in the settings, you can still merge the review even if two or more approvals are required. As the author, you will supersede the settings, since the self-review option is enabled.