> 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/sending-test-case-for-review.md).

# Sending Test Case for Review

To send test case for review, perform the following actions:

1. On the **Home** page, under **Projects**, select the required project.
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="/files/LmSZgIUJXs1p6dUCqkQD" 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.

<figure><img src="/files/Z5LyBFOkifaiKNStYwPz" alt=""><figcaption></figcaption></figure>


---

# 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/sending-test-case-for-review.md?ask=<question>&goal=<endgoal>
```

`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.