> For the complete documentation index, see [llms.txt](https://docs.mozark.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mozark.ai/no-code-studio/running-and-reporting/reports.md).
# Reports
What happened, on which device, and where it went wrong.
## The reports list
**Test Reports** lists every job for the project, newest first: the suite name, when it ran, the platform and its overall status. Click a job to open its report.
## The job report
The top of the report summarises the run: who ran it, the run type, the app, the project, the duration, and a pass-rate chart, with Rerun and Get Shareable Link alongside.
Below it is the **Test cases table**:
* One **row** per test case
* Columns: Test case, Status, Device, Duration
```
Test case Status Device Duration
TC-01 Passed Samsung A50 1m 12s
TC-01 Passed Redmi 9 1m 10s
TC-01 Failed Samsung M12 1m 18s
```
This layout answers the question that matters most: **is this a broken test, or a broken device?** The same test case failing on every device is a test problem. Every test case failing on one device is usually a device or build problem.
## Statuses
| Status | Meaning |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Passed | Every step succeeded |
| Failed | A step failed, or an assertion did not hold |
| Did not run | The test never started, usually because the app never installed or launched. See [Troubleshooting](https://docs.mozark.ai/no-code-studio/reference/troubleshooting) |
| Running | Still executing |
| Skipped | Not executed in this run |
| Completed | Finished, without a pass/fail verdict |
## Session details
Click any row to open that session: one test case on one device. Five tabs:
| Tab | What is in it |
| ----------- | -------------------------------------------------------------------------------------------- |
| Steps | Every step in order, with its status and timing. Expand a step to see its individual actions |
| Screenshots | Every screenshot captured during the session |
| Video | A recording of the whole session, if session video was enabled |
| Files | Logs and other artefacts produced by the run |
| Info | Device, app, session and run metadata |
## Reading a failure
1. Open **Steps** and find the **first** failed step. Later failures are usually consequences of the first one.
2. Look at the step's screenshot. Most failures are obvious from the picture: the app was on a different screen, a dialog was in the way, the button moved.
3. If the screen looks right but the step still failed, the locator did not match. See [Troubleshooting](https://docs.mozark.ai/no-code-studio/reference/troubleshooting).
4. If the screen looks wrong, scrub the **Video** back a few seconds to see how it got there.
{% hint style="info" %}
The first failure is the real one. A test that fails at step 4 will usually fail every step after it too, because the app is no longer where the test thinks it is.
{% endhint %}
## Capturing more, or less
What ends up in a report is chosen when you start the session, in Advanced settings on the **Test Creation** screen:
| Capability | Effect on the report |
| -------------------- | ------------------------------------ |
| Record Session Video | Adds the **Video** tab |
| Step Screenshots | Populates the screenshot timeline |
| Capture Device Logs | Adds logcat / syslog to **Files** |
| Capture Network Logs | Adds network traffic to **Files** |
| Capture App Profile | Adds CPU, memory and battery samples |
The defaults capture everything useful. Turn things off only if you have a specific reason.
---
# 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.mozark.ai/no-code-studio/running-and-reporting/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.
