> For the complete documentation index, see [llms.txt](https://docs.testwheel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testwheel.com/test-results.md).

# Test Results

This Page describes about the Test Results page in TestWheel application.

Users can access the **Test Results** by clicking the corresponding icon in the left-side navigation bar. Upon clicking, users will be able to view a comprehensive list of all previously executed tests along with their detailed reports.

* **Functional Tests**:\
  For functional test executions, users can:
  * View and download **PDF reports**
  * Watch **test execution videos**
  * Access detailed **bug reports**
    * From the bug report view, users can directly create bug tickets in **Azure** and **Jira**, streamlining the issue-tracking process.
* **REST API Tests**:\
  For REST API test executions, users can:

  * **Download PDF reports**
  * Check the **test execution status** for each API test

  <figure><img src="https://4225752331-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfpdbhL4mnjdXkFbYOzps%2Fuploads%2FqoQqV6juGT7eJtXRFasZ%2Fimage.png?alt=media&amp;token=27e5f8a3-fdb8-4690-8ab6-b8702f4b522d" alt=""><figcaption></figcaption></figure>

This feature offers users a centralized and user-friendly way to track test outcomes, review detailed evidence, and initiate bug tracking actions seamlessly.


---

# 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.testwheel.com/test-results.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.
