# Review Test Case

The **Send for review** feature in Avo Assure enables users to submit a test case for evaluation or validation by another team member.

{% hint style="info" %}
**Note:**

* A Testcase is always sent to review only to a user with the role As Quality Manager or Quality Lead in Avo Assure.
* Ensure that the selected reviewer is a member of the same project.
  {% endhint %}

## **Steps to send Test case for review**

1. On the **Home** page, under **Projects**, select the required project.&#x20;
2. Navigate to **Design Studio** and select the **Testcase** for which you want to view the version history.
3. Select Ellipsis **(...)** icon.
4. Select **Send for review** from the dropdown.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FgJ1S54bUwOaLZP5OmfgV%2Fimage.png?alt=media&#x26;token=833b809a-a09b-4320-bf42-1abd11a2324e" alt=""><figcaption></figcaption></figure>

5. Select **Reviewer** from the dropdown.
6. Add review comments in the text box and select **Send for review**.

{% hint style="info" %}
**Note:** Once the Testcase is sent for validation to the manager or lead, it gets locked as the **locking mechanism feature** in Avo Assure gets activated. It gets unlocked only after the manager or lead decline it. Only then, the user who had requested the review can **delete** or **modify** the Testcase.
{% endhint %}

When a Testcase is sent for review, the user requesting the review loses access to it as the **locking mechanism feature** in Avo Assure gets activated for the Test Case.&#x20;

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F5cei2GVVbylUAIZIeW18%2Fimage.png?alt=media&#x26;token=cfd24a5d-0c2a-4927-a38a-b1f0c78a66b5" alt=""><figcaption></figcaption></figure>

## To be Reviewed&#x20;

{% hint style="info" %}
**Note:** To review the Element Repository, Execution List, and Data Table, follow the same steps as described below.&#x20;
{% endhint %}

#### Steps to Approve or Decline the Testcase (For reviewer):&#x20;

When a sender sends a Testcase for review, the reviewer can access it in two ways:&#x20;

### **A. Manual Navigation**

1. On the **Home** page, under **Projects**, select the desired project. &#x20;
2. Select **Design Studio**, navigate to the **Testcase** tab.
3. Select Test case which is sent for review. A pop-up titled **Review Test Case** appears.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FPlb66OeZy1FcOhnCMgSW%2Funknown.png?alt=media&#x26;token=91300630-8726-4cac-9709-7ce0496b29c0" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Note**:&#x20;

* When a Test case shared for review is deleted, renamed, or moved to a different folder, the system shows a notification explaining the reason for the change.&#x20;
* The system clears the notification after displaying the message and selecting **OK**, ensuring that reviewers do not access invalid or outdated Test case links. As shown in below image.
  {% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F2dyGtspVClUynWV0cha0%2Fimage.png?alt=media&#x26;token=70b4a130-9462-49c3-9c89-982f902335ee" alt=""><figcaption></figcaption></figure>

4. Select **Approve**/**Decline** action&#x20;

&#x20;       **i.  Approve:**&#x20;

&#x20;           1\. Select **Approve** to approve the test case.&#x20;

{% hint style="info" %}
**Note**: After a reviewer approves, the Testcase dose not reassign to the sender. The sender can reassign it to themselves if needed.
{% endhint %}

&#x20;        **ii.  Decline:**&#x20;

&#x20;             1\. Select **Decline** to reject the test case. The **Reason for Rejection** pop-up appears.

&#x20;             2\. Enter the rejection reason and select **Submit**.

{% hint style="info" %}
**Note:**  When a reviewer declines, Avo Assure reassigns the Testcase to the sender along with the rejection reason for further action.
{% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2Ft8jf51en1OmvdUWHXAJl%2Funknown.png?alt=media&#x26;token=fa2632a6-0779-4790-a238-e6c38b555042" alt=""><figcaption></figcaption></figure>

### B. Via Notification

1. On the **Home** page, navigate to the **Review Notification** icon available in the upper-right corner, and the receiver can view all assigned test case review requests.&#x20;
2. Select **Review** option from the notification list for the specific Testcase to review.

{% hint style="info" %}
**Note:** &#x20;

* The total number of review requests displays above the icon and updates automatically when Testcases are approved or declined.
* Each review request shows the Testcase name, Project name, Requester name, and Timestamp.&#x20;
* For each request, the reviewer can choose **Review**, **Approve Changes**, or **Decline Changes** directly from the notification.&#x20;
* When a Test case shared for review is deleted, renamed, or moved to a different folder, the system shows a notification explaining the reason for the change.&#x20;
* The system clears the notification after displaying the message and selecting **OK**, ensuring that reviewers do not access invalid or outdated Test case links.
  {% endhint %}

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F7QCsdMXUfqCf8IFHauD9%2Funknown.png?alt=media&#x26;token=bf14a67c-d9df-46a9-958f-a45c2eac8bf6" alt=""><figcaption></figcaption></figure>

3. The selected Test case tab opens, and the test case Information Panel displays the relevant details for review.&#x20;

The following section provides a detailed description of the information displayed in the panel:

* **Created On**: Shows the date and time when the Testcase was created. Helps track when the Testcase was developed.&#x20;
* **Created By**: Displays the name of the user who created the Testcase. Useful for knowing who created it.
* **Modified On**: Indicates the most recent date and time the Testcase was modified. Helps reviewers to check for recent changes before reviewing.
* **Modified By**: Shows the name of the user who last modified the Testcase. Useful to identify who made the most recent changes.
* **Status**: Displays the current review state of the test case, such as Under Review, Approved or Decline. This helps track the progress in the review process.
* **Comments**: A custom message added by the user who requested the review, usually to describe the purpose, functionality, or specific points to be checked in the test case.&#x20;

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F01ROT1GWbGRxe3SKBmhl%2Funknown.png?alt=media&#x26;token=1b176559-fec1-4e14-99e7-8187bbaeef50" alt=""><figcaption></figcaption></figure>

4. Select **Approve**/**Decline** action to Approve or Decline the request.&#x20;

{% hint style="info" %}
**Note:**&#x20;

* **Approve**: After a reviewer approves, the Testcase dose not reassign to the sender. The sender can reassign it to themselves if needed.
* **Decline**: When the reviewer declines, the Avo Assure reassigns the Testcase to the sender along with the rejection reason for further action.
  {% endhint %}

5. After selecting **Approve** or **Decline**, a pop-up message appears confirming the action: **The Test case has been approved** or **The Test case has been rejected**.
