> 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/debugging-tests/runs-history.md).

# Runs history

Explore BugBug's Runs History for efficient test debugging. Access logs, track progress, and review your past tests and suites runs. Try it now!

## Why use runs history?

In the "Runs history" tab you can review your past tests and suites runs. Access the reports, errors, and logs of your runs to debug them.

* review past runs (both local and cloud)
* clear history
* stop all running tests
* navigate to a specific test that fails
* download test run and suite run reports

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FmiJUVMT1Qj87diXt9wTr%2Fimage.png?alt=media&amp;token=43784f75-1095-425b-a8d9-ab65552b0bc2" alt=""><figcaption></figcaption></figure>

In the runs history view, you are able to filter test runs and suite runs by:

* status (Passed, Failed, Error, Running, Stopped, Queued, Skipped)
* profile
* method (Cloud, Local browser)
* screen (Desktop, Mobile)
* auto-retry
* error code ([list here](/debugging-tests/error-codes.md))
* run by
* run date

{% hint style="info" %}
**Important!** The "Tests" tab also shows tests initiated via a suite. This tab simply shows all your past test runs.
{% endhint %}

## Read-only test details

When you click a test in the "Runs history" it will open its details in a read-only mode. This is because your current version of the test might be different that the one you're reviewing.

To quickly jump to the most up-to-date version of this test, click the "Go to test" button.

![](https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FFjNTNzAW0ix2APsDvXnA%2FScreenshot%202022-04-12%20at%2010.07.17.png?alt=media\&token=081646d2-dfdf-4992-b08e-8608d4501486)

## Dates and times

| Shown in BugBug                                                         | Timezone                                                                                                          |
| ----------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Start and end time in a run's details                                   | The project's timezone, set in [Project settings → General](/preventing-failed-tests/project-settings.md#general) |
| Relative times, such as "5 minutes ago", and the dates next to statuses | Your browser's timezone                                                                                           |
| [Schedule](/running-tests/schedules.md) hours                           | The project's timezone                                                                                            |

If your browser's timezone differs from the project's, the start time in a run's details can differ from the time you see elsewhere. The project timezone doesn't change the browser's clock during a test.

## Download a suite run report

When you enter a specific test suite details page apart from the general information, execution statuses, and so on, you can also download a report with a summary.

Simply click the "**Download report**" button and select the report type to generate and download one.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FCe0rcIJMUv6AjW48RnTd%2F1downloadButton.png?alt=media&amp;token=8e30ce38-c381-47f7-929a-53b0402faf26" alt=""><figcaption></figcaption></figure>

As a next step, you can add additional information eg. a reason why some tests are skipped.

<figure><img src="https://3168433179-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MKixgeBPbLvnD0l1eiV%2Fuploads%2FTWPYqyXGZ9puHa2hM2CH%2F1confirmationModal.png?alt=media&amp;token=2e74c8bb-1bbb-4808-8039-47ccc68bc842" alt=""><figcaption></figcaption></figure>

When you confirm the action, the report is downloaded, and you can preview it locally or share it with other related parties.

Learn more about the available formats in [Standard reports](/organizing-tests/reporting/standard-reports.md) and [Advanced reports](/organizing-tests/reporting/advanced-reports.md).

## How long runs are kept

| Data                                                                                                           | Kept for                                                                                                                                 |
| -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Test runs and suite runs, with their results and step [screenshots](/debugging-tests/screenshots.md)           | Depends on your plan: 7 days on Free, 1 month on Core, 2 months on Pro, 3 months on Business. See [pricing](https://bugbug.io/pricing/). |
| [Console logs](/debugging-tests/console-logs.md) and [network logs](/debugging-tests/network-logs.md) of a run | 3 days                                                                                                                                   |
| [DOM snapshots](/debugging-tests/dom-snapshot.md) of a failed step                                             | 7 days                                                                                                                                   |
| [Advanced report](/organizing-tests/reporting/advanced-reports.md) download links                              | 24 hours                                                                                                                                 |

Runs older than your plan's history aren't available anymore, and their screenshots are deleted with them. Logs and DOM snapshots are deleted when they expire; the run itself stays in the history, without them. Download a [report](/organizing-tests/reporting/standard-reports.md) if you need to keep the results longer.

## Clear history

**Clear history** permanently deletes the runs from the history, including their screenshots. It can't be undone. Download the reports you need first.

## FAQ

<details>

<summary>How long does BugBug keep run history?</summary>

7 days on Free, 1 month on Core, 2 months on Pro and 3 months on Business. Console and network logs are kept for 3 days, DOM snapshots for 7 days.

</details>

<details>

<summary>How long are screenshots kept?</summary>

As long as the run they belong to: they're deleted together with the run, when it's older than your plan's history or when you clear the history. To keep them longer, download an [advanced report](/organizing-tests/reporting/advanced-reports.md) with screenshots (Business plan).

</details>

<details>

<summary>What happens when I clear the history?</summary>

The runs are deleted permanently, together with their results and screenshots. You can't restore them.

</details>

<details>

<summary>How do I keep results longer than the history allows?</summary>

Download a report of the run: a [PDF summary or JUnit XML](/organizing-tests/reporting/standard-reports.md), or on the Business plan an [advanced report](/organizing-tests/reporting/advanced-reports.md) with screenshots, CSV or JSON.

</details>

<details>

<summary>Which timezone are the times in runs history in?</summary>

Start and end times in a run's details are in the project's timezone. Relative times, such as "5 minutes ago", follow your browser's timezone. See [Dates and times](#dates-and-times).

</details>


---

# 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/debugging-tests/runs-history.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.
