> For the complete documentation index, see [llms.txt](https://docs.qatts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.qatts.com/v-2.0/test-execution/automated-test-execution/scheduling-test-runs.md).

# 4.2.2 Scheduling Test Runs

On the dash board click on the **Schedule Test Task.**

 

![](/files/-Mbevx8NWcjYREBz1VwK)

On click on the “Schedule test task”, the page should appear as also shown in the screenshot below. Then Click on “**Add Schedule Task**”.

![](/files/-Mbevx8ObGzTC3Uuzltk)

Enter the Job name, select the test task name and the schedule the job

After fill the details click on the **Save** button.

![](/files/-Mbevx8PJWsuVm9DdARu)

The Schedule test task should be created successfully for you and Created Schedule test task displayed in the grid. a page similar to the screenshot below should appear.

![](/files/-Mbevx8QsJvCZ5Fvrjxw)


---

# 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.qatts.com/v-2.0/test-execution/automated-test-execution/scheduling-test-runs.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.