> 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/azure-devops-in-avo-assure/updating-and-viewing-reports-in-azure-devops/viewing-reports-in-azure-devops.md).

# Viewing Reports in Azure DevOps

To view execution reports in Azure DevOps, perform the following actions:

1. Login to Azure DevOps.
2. Select Project.
3. Hover on **Test Plan** icon from left pane and select **Test Plan**.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F7M5lV0gIulfIdbs4zzBo%2Funknown.png?alt=media&amp;token=c969fe0b-bffc-4e11-a185-df378847832b" alt=""><figcaption></figcaption></figure>

4. On the **Test Plans** page, from **All** tab, select the mapped Test Plan.
5. On the **Test Suits** page, select the Test Suite. In right pane Test Suite opens.
6. Hover on executed Test case, select **More options** icon.
7. Select **View execution history**. The execution report opens.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2F0F3dZJX0JEaFxJyuw3yK%2Funknown.png?alt=media&amp;token=86f7f9e1-e352-4c79-aa7c-549ed5adddce" alt=""><figcaption></figcaption></figure>

8. You can view the details of the execution.

<figure><img src="https://2174257472-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fk8QZzXZMIJSStKAzDSTu%2Fuploads%2FbgDZU16Nae94Yy8Jgsem%2Funknown.png?alt=media&amp;token=4b2c7616-6e3e-4270-a8cd-b4d545e41108" 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 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/azure-devops-in-avo-assure/updating-and-viewing-reports-in-azure-devops/viewing-reports-in-azure-devops.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.