> 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/support-resources/faqs/design-studio/reports.md). # Reports Use this section to view common questions related to reports and analysis. It includes queries about generating reports, interpreting results, analyzing test outcomes, analyzing failures, and monitor the overall status of test runs. * **Do reports provide step-level execution details?**\ **Ans**: Yes. Reports include step-level information that shows the status of every action executed in a test case. Each step displays whether it passes, fails, or is skipped. * **Are execution results available in the Reports tab?** **Ans**: Yes. The **Reports** displays the results of executed test cases and shows whether each test case passes or fails after execution. * **Are reports automatically generated before test execution?** **Ans**: No. Reports are generated only after test case execution completes. The system records the results during execution and then makes them available in the [Reports](/avo-assure/create-and-execute-tests-with-design-studio/working-with-reports-section.md). --- # 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/support-resources/faqs/design-studio/reports.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.