> For the complete documentation index, see [llms.txt](https://docs.ratl.ai/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ratl.ai/guide/features/run-history.md).
# Run History: Tracking and Managing Your Test Executions
The **Run History** feature in **Ratl** enables users to track and analyze the execution history of their tests across **Functional Tests**, **Integration Tests**, **Load Tests**, and **Accessibility Tests**. This feature provides a detailed log of past executions, making it easier to identify and address issues.
***
### **Key Benefits**
* **Comprehensive Execution Logs**: Provides a complete history of test executions for easy reference.
* **Version Tracking**: Allows users to track the test execution history for specific versions.
* **Quick Re-execution**: Enables re-execution of specific tests directly from the run history.
* **Issue Resolution Insights**: Helps identify when and where issues occurred and when they were resolved.
***
### **How to Use the Run History Feature**
#### **Step 1: Navigate to the Run History**
* Navigate to the desired test type (e.g., Functional Tests).
* Select the specific test suite and click on **Run History** from the **Actions Menu**.
#### **Step 2: Review Execution History**
* View the list of all past executions for the selected test suite.
* Users can access details such as:
1. **Test Case Name**: Name of the test case executed.
2. **Triggered On**: Date and time when the test was triggered.
3. **Triggered By**: Method of triggering (e.g., scheduled, manual).
4. **Status**: Status of the test execution (e.g., Passed, Failed).
#### **Step 3: Re-execute Tests**
* Select a specific execution from the history.
* Click on **Run** to re-execute the selected test case.
* Monitor the status of the re-executed test to verify if issues have been resolved.
***
### **Postconditions**
* Users can analyze the complete execution history of their tests.
* Any failed tests can be re-executed to validate fixes.
* Provides insights into version-specific issues, helping teams identify patterns and trends.
***
### **Expanding Run History Across Features**
The Run History feature works seamlessly across all test types:
1. **Functional Tests**: Track execution history for functional validations.
2. **Integration Tests**: Monitor execution trends and resolve integration-specific issues.
3. **Load Tests**: Access historical performance metrics to ensure system reliability.
4. **Accessibility Tests**: Verify accessibility compliance across versions and re-run failed tests.
Each feature follows the same process as described above, ensuring a consistent user experience.
***
### **Conclusion**
The **Run History** feature in **Ratl** empowers teams to efficiently manage and analyze test executions. By offering detailed insights into execution history, it helps streamline testing workflows and accelerates issue resolution.
---
# 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.ratl.ai/guide/features/run-history.md?ask=&goal=
```
`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.