> 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.md).

# Zephyr

Integrating Zephyr with Avo Assure enhances the test management framework of Avo Assure. Each test execution in Avo Assure can be linked to Zephyr's test cases, which makes it easier to track the status of the execution. The integration of Zephyr in Avo Assure is unidirectional. This improves efficiency and collaboration within QA phase.

### This document includes:

[Prerequisites](/avo-assure/integrations-in-avo-assure/test-management/zephyr/prerequisites.md)

Pre-requisites for Zephyr Integration

[Zephyr Integration in Avo Assure](/avo-assure/integrations-in-avo-assure/test-management/zephyr/zephyr-integration-in-avo-assure.md)

Steps to integrate Avo Assure with Zephyr

[Execute Test Case through Zephyr](/avo-assure/integrations-in-avo-assure/test-management/zephyr/execute-test-case-through-zephyr.md)

Steps to create execution list and execute it in Zephyr

[Execution Status in Zephyr](/avo-assure/integrations-in-avo-assure/test-management/zephyr/execution-status-in-zephyr.md)

Steps to view status of execution in Zephyr


---

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