> 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. Go to **Design Studio** and select the Testcase for which you want to view the version  history.
3. Select the **See more** (**...**) icon next to the created test case.
4. Select **Send for review** from the dropdown. The **Test Case Name** dialog opens.
5. Select reviewer from the **Select Reviewer** dropdown.
6. Enter the comment in the **Review Comments** text box.
7. Select **Send for review**.

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

* When a Test Case is sent to a manager or lead for review, it is locked for the user who sends it. 
* The sender cannot modify or delete the Test Case while it is under review.
* The sender can send the Test Case for review to multiple reviewers. 
* If the sender tries to assign a Test Case that is under review to another user, a confirmation message appears stating that the review will be revoked.
  {% endhint %}

<img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FGvTjlR3a8YEgcnJj2cvd%2Funknown.png?alt=media&amp;token=c6fae5a6-0837-4ceb-a197-b6b5907fe76b" alt="" height="282" width="405">


---

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