> 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**

<figure><img src="https://3939944954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FefV6n9Vxvs062CsQhtKk%2Fuploads%2Fpa7GvyL3JCFohmgFvhIx%2FrunHistory1.png?alt=media&amp;token=d6be013e-4302-4c52-9634-c85d2b65a55a" alt=""><figcaption></figcaption></figure>

* 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**

<figure><img src="https://3939944954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FefV6n9Vxvs062CsQhtKk%2Fuploads%2FzGuOZ1kjtvhJ9WDym9Qz%2FrunHistory2.png?alt=media&amp;token=a3f983e3-83fb-4b4b-96b7-829d14e2912a" alt=""><figcaption></figcaption></figure>

* 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.