> For the complete documentation index, see [llms.txt](https://docs.avoautomation.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/features-in-test-case-section-1/review-test-case/reviewing-test-case.md).
# Reviewing Test Case
{% hint style="info" %}
**Note:** To review the Element Repository, Execution List, and Data Table, follow the same steps as described below.
{% endhint %}
#### Steps to Approve or Decline the Testcase (For reviewer):
When a sender sends a Testcase for review, the reviewer can access it in two ways:
### **A. Manual Navigation**
1. On the **Home** page, under **Projects**, select the desired project.
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.
{% hint style="info" %}
**Note**:
* 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.
* 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 %}
4. Select **Approve**/**Decline** action
**i. Approve:**
1\. Select **Approve** to approve the test case.
{% 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 %}
**ii. Decline:**
1\. Select **Decline** to reject the test case. The **Reason for Rejection** pop-up appears.
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 %}
### 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.
2. Select **Review** option from the notification list for the specific Testcase to review.
{% hint style="info" %}
**Note:**
* 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.
* For each request, the reviewer can choose **Review**, **Approve Changes**, or **Decline Changes** directly from the notification.
* 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.
* 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 %}
3. The selected Test case tab opens, and the test case Information Panel displays the relevant details for review.
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.
* **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.
4. Select **Approve**/**Decline** action to Approve or Decline the request.
{% hint style="info" %}
**Note:**
* **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**.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.avoautomation.com/avo-assure/create-and-execute-tests-with-design-studio/working-with-test-case-section/features-in-test-case-section-1/review-test-case/reviewing-test-case.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.