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

# Check Test History

Check the details of the earlier site performance tests conducted. Check history by performing the following steps:

1. Click the test suite in which you want to initiate a test.

![checkhistory](https://ingest-lab.netlify.app/images/siteperformanceimages/addnewlighthousevariant.png)

2. Click **Show Test History** at the top right of the screen.

![checkhistory](https://ingest-lab.netlify.app/images/siteperformanceimages/showtesthistory.png)

3. The following list of tests appears along with the date and the time of the site performance test. The latest test is the first on the list.

![varianttesthistory](https://ingest-lab.netlify.app/images/siteperformanceimages/varianttesthistory.png)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ingestlabs.com/site-performance/configure-variants/check-test-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
