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

# Reporting

Download test run and suite run reports from BugBug: PDF and JUnit XML on all paid plans, detailed PDF with screenshots, CSV, JSON and ZIP on Business.

BugBug generates reports for both **test runs** and **suite runs**. You can download them from [Runs history](https://docs.bugbug.io/debugging-tests/runs-history.md) with the **Download report** button on a run's details page.

### Which report do I need?

|                | [Standard reports](https://docs.bugbug.io/organizing-tests/reporting/standard-reports.md) | [Advanced reports](https://docs.bugbug.io/organizing-tests/reporting/advanced-reports.md) |
| -------------- | ----------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------- |
| Formats        | PDF summary, JUnit XML                                                                    | Detailed PDF with step-by-step screenshots, CSV, JSON, ZIP with screenshots               |
| Plan           | All paid plans, starting from Core                                                        | Business                                                                                  |
| How you get it | Downloaded right away from the **Download report** button                                 | Generated in the background; you get a download link by email, valid for 24 hours         |
| Best for       | Sharing a quick summary, feeding results into test tooling                                | Audits and compliance documentation, data analysis, sending results to other systems      |

Both report types let you add a custom note before downloading, for example the reason why some tests were skipped.

### Reports outside the app

If you run tests from a CI/CD pipeline, you can generate a JUnit XML report without opening BugBug:

* With the [CLI](https://docs.bugbug.io/integrations/cli.md) (Pro plan and higher), add `--reporter junit --output-path report.xml` to `bugbug tests run` or `bugbug suites run`, or download a report for an existing run with `bugbug testruns report` or `bugbug suiteruns report`.
* With the [Public API](https://docs.bugbug.io/integrations/public-api.md) (Business plan), download JUnit reports for test runs and suite runs programmatically.

### Check test stability without a report

To see at a glance whether a test or suite is getting flaky, use [Run history charts](https://docs.bugbug.io/debugging-tests/run-history-charts.md). They show the recent runs and the success rate on the Tests and Suites lists, without downloading anything.

### Learn more

* [Standard reports](https://docs.bugbug.io/organizing-tests/reporting/standard-reports.md)
* [Advanced reports](https://docs.bugbug.io/organizing-tests/reporting/advanced-reports.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.bugbug.io/organizing-tests/reporting.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.
