# Runs history
## 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 a suite run report
{% 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.
## 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 just click on the "**Download PDF report**" button to generate and download one.
As a next step, you can add additional information eg. a reason why some tests are skipped.
When you confirm the action, and save the file as PDF you can locally preview it or share it with other related parties.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.bugbug.io/debugging-tests/runs-history.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.