# Schedules: Automate and Manage Test Execution Timing

The **Scheduling Test Executions** feature in **Ratl** allows users to plan and automate the execution of their test suites for **Functional Tests**, **Load Tests**, **Integration Tests**, and **Accessibility Tests**. This ensures that tests are executed at the desired time intervals without requiring manual intervention. Below are the details for creating and managing schedules, referenced for **Functional Tests**.

<figure><img src="/files/jf2ikUxcEomprw4X7Txv" alt=""><figcaption></figcaption></figure>

***

### **Key Benefits**

* **Automated Execution**: Enables automated test suite executions without manual triggers.
* **Customizable Scheduling**: Supports daily, weekly, and monthly frequencies.
* **Centralized Management**: Allows users to view, edit, activate, or delete schedules in one place.
* **Execution Tracking**: Provides detailed run history for each schedule to track the test status.

***

### **Preconditions**

Before creating a schedule, ensure the following:

* The test suite is ready and functional.
* Define the frequency (daily, weekly, or monthly) and time for execution.

***

### **How to Use the Scheduling Feature**

#### **Step 1: Select the Test Suite**

<figure><img src="/files/onI65uuf6k5G7KTl0i3C" alt=""><figcaption></figcaption></figure>

* Navigate to the **Functional Test** page (or any relevant test type).
* Identify the test suite for which you want to create a schedule.
* Click on the **Actions Menu** (three dots) next to the test suite and select **Schedule Test**.

#### **Step 2: Enter Schedule Details**

<figure><img src="/files/DpcGFNCtxmNY92YNI1e8" alt=""><figcaption></figcaption></figure>

* Provide the following details in the **Schedule Test** popup:
  1. **Schedule Name**: Give a unique name to the schedule.
  2. **Frequency**: Select the frequency of execution (Daily, Weekly, Monthly).
  3. **Start Date** and **End Date**: Specify the schedule duration.
  4. **Time**: Set the time for the test execution.
* Once all details are entered, click **Create** to save the schedule.

#### **Step 3: View and Manage Schedules**

<figure><img src="/files/UHEmkCYCzVlWZkq7n68a" alt=""><figcaption></figcaption></figure>

* After creation, you are directed to the **Schedules Listing Page**.
* The listing page provides:
  1. **Schedule Details**: Displays the name, created date, created by, frequency, and status (active/inactive).
  2. **Actions Menu**: Allows users to edit, deactivate, or delete schedules. You can also view the run history of the schedule.

#### **Step 4: Monitor Execution**

<figure><img src="/files/jBcQfD1A3bSux5h5FNRB" alt=""><figcaption></figcaption></figure>

* Scheduled executions happen automatically at the specified time.
* Navigate to the **Run History** to analyze past executions:
  * View the triggered date and time.
  * Check the status of each execution (e.g., Passed/Failed).

***

### **Postconditions**

* Scheduled tests are executed as per the configured frequency and time.
* All execution results are logged in the **Run History** for tracking.
* Schedules can be edited or deleted if changes are required.

***

### **Expanding Scheduling Across Features**

The scheduling feature can be applied across other test types, including:

1. **Functional Tests**: Schedule regular functional test executions to systematically verify the accuracy and reliability of your application.
2. **Integration Tests**: Ensure seamless integration testing by setting regular schedules.
3. **Load Tests**: Automate performance assessments by scheduling load test executions.
4. **Accessibility Tests**: Plan periodic accessibility checks to maintain compliance.

Each feature follows the same process as described above, ensuring uniformity and ease of use across the platform.

***

### **Conclusion**

By using the scheduling feature in **Ratl**, teams can ensure timely and consistent execution of their test suites. This not only improves efficiency but also enhances the reliability of test results by reducing manual efforts.


---

# 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.ratl.ai/guide/features/schedules.md?ask=<question>
```

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.