> 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/integrations-in-avo-assure/test-management/zephyr/execute-test-case-through-zephyr.md).
# Configuring and Executing Test Case through Zephyr
Step-by-step process to execute Test Case through Avo Assure:
1. On **Execution** tab, Create **Execution** List
2. Select and Drag **Test Case** from Test Cases window
3. On the configuration window, select **Client** and **Browser** from their respective dropdown
4. Select **Zephyr** as Test Management Tool, **Zephyr** pop up window will appear then enter credentials and click **Save** button from the pop up
5. Click **Save** button to create Execution List successfully
6. Click **Execute** button, then auto populated Execute Now window appears on the screen
7. Click **Execute** button to start the execution
{% hint style="warning" %}
***Note:** If user have already selected Test Management Tool while configuring the execution list then it will auto populated*
{% endhint %}
After execution user can see the message in Avo Assure Client, like Updated Zephyr details.
---
# 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/integrations-in-avo-assure/test-management/zephyr/execute-test-case-through-zephyr.md?ask=&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.
