Test Case Review

In Qase, it is possible to ensure that the Test Cases being created are first being verified by someone superior, be it a QA team manager, supervisor, CTO, or else.

In the Project Settings, you can define several options regarding Test Case Review:

• Review enabled: review is enabled or disabled for the project
• Review is mandatory: for anyone creating a new Test Case, it will not be possible to create it without passing a review.
• Self merge: with this option turned on, the creator of a review will be able to merge review requests themselves.
• Approves required: set a threshold for how many reviewers should approve a submitted Test Case before being added to the repository.

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 on 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 "Case Review" section:
  
  NB: as seen on the screenshot, you can create Reviews not only for the new Test Cases but also submit any updates introduced into an existing Test Case for review - "Type" column illustrates whether a review is for a new case or an update.
  
  
• From the "Case 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:
  
  • The author will be able to "Merge" (if Self-merge is allowed, and if the threshold of approvals has been hit), "Edit" or "Decline" a review, as well as assign it to someone else in the team:
    
  • A non-authoring reviewer will have options to "Merge" (which activates when a specific number of mandatory approvals get achieved, if it has been set in Project settings), "Approve/Unapprove", "Request Changes" or"Decline", as well as add someone else as a reviewer:
    
• Both a review author and other reviewers can leave comments and see others' comments left before.

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.

Review assignment

It is possible to assign a review to a specific user of the workspace (given that they have the necessary permission granted by their Role).

Once a review request has been generated, both the author of the changes and any other users with the permissions to access and make decisions on reviews will be able to assign a review to specific users.

Even if a review request has someone specific assigned to review the changes, any other users with the necessary permissions can still perform the actions available to a reviewer, albeit non-assigned: Merge, Approve/Unapprove, Decline, Request Changes or assign a reviewer.