> 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

The review process in Avo Assure allows assigned reviewers to check a test case before it is approved for further use. Reviewers can review the test case details, approve the test case, or decline it with a reason when changes are required. This article explains how to access, review, approve, and decline a test case submitted for review.

{% hint style="info" %}
**Note**: The same steps apply when reviewing **Element Repository**, **Execution List**, and **Data Table**.
{% endhint %}

To access a test case from **Review Notifications**, perform the following actions:

1. On the **Home** page, select the **Review Notifications** icon in the upper-right corner. 
2. Locate the required review request. 
3. Select **Review**. The **Details** tab opens. \
   The following section provides a detailed description of the information displayed in the panel:
   * **Test Case Name**: Displays the name of the test case.
   * **Description**: Displays the description of the test case. 
   * **Status**: Displays the current status of the test case, such as **Under Review**.
   * **Comments**: Displays comments added for the test case. 
   * **Created On**: Displays the date and time when the test case was created. 
   * **Created By**: Displays the name of the user who created the test case.
4. Select **Approve** or **Decline**.

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

* Reviewer can add a comment for the declined test case. 
* Reviewer can review the test case by navigating directly to the project.
* The number displayed above the **Review Notifications** icon shows the number of pending review requests. 
* Each review request displays the **Test Case Name**, **Project Name**, **Requester Name**, and **Timestamp**. 
* You can select **Review**, **Approve Changes**, or **Decline Changes** directly from the notification.
* If the test case is deleted, renamed, or moved to another folder after it is sent for review, Avo Assure displays a notification explaining the change. Select **OK** to close the notification.
  {% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
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=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.