> 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/features-in-report-section/view-screenshot.md).
# Viewing Screenshot in Report
To view screenshots in Reports there are two ways:
* Selecting **view Reports** Option in Testcase Details
* Selecting **PDF with Screenshot** option in Download Testcase Details
### Selecting V**iew Reports** **Option** in Test Case Details
To select the view Reports in Test case Details, perform the following actions:
1. On **Home** page, from **Projects**, select required project. and
2. Select **Design Studio**.
3. Select **Reports** tab.
4. On **Reports** tab, expand folder and select Test case.
5. From right side column, select **Testcase Details** icon.
6. From **Run Details** pop up, select **view Reports** icon.
7. On **Result Summary** page, under **Action** column, select **View Screenshot**.
### Selecting **PDF with Screenshot option** in Download Test Case Details
To select PDF with Screenshot in Download Test Case Details, perform the following actions:
1. On **Home** page, from **Projects**, select required project.
2. Select **Design Studio**.
3. Select **Reports** tab.
4. On **Reports** tab, expand folder and select Test case.
5. From right side column, select **Testcase Details** icon.
6. From **Run Details** pop up, select **Download Testcase Details** icon.
7. Select **PDF with Screenshots**. Reports PDF gets downloaded in your system.
8. In your system, select **Downloads** folder and select recent downloaded PDF.
9. In PDF report, to view the screenshot, select the screenshot added after every step.
---
# 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/features-in-report-section/view-screenshot.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.
