> 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-reports-section/read-a-report.md). # Viewing a Report The Viewing a Report section helps you review the results of test executions in Avo Assure. It provides detailed execution information, including the overall result summary, step-level execution details, and orchestration action reports. You can also access reports received through email to review execution outcomes. This article explains how to view execution reports, understand result summaries, access reports through email, and review orchestration action reports. {% hint style="info" %} **Enhancements:** * There is a new column added in report as **Error Details**, it provides detailed **error description** for the failed steps. * The report is available in the format like **HTML**, **PDF**, **detailed PDF**, and **email notification** report as well. * The error details are provided for **Grid**, **Excel**, **textbox operations**, **Dropdown** and **radio, checkbox** operations related actions. * We have also provided the error details for Verify and compare related action in previous release. * For each **GetParam** step with status, value, and parameter name. Failures include error details, logs, and screenshots, with filter support for quick issue tracking. {% endhint %} --- # 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-reports-section/read-a-report.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.