> For the complete documentation index, see [llms.txt](https://docs.testery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testery.io/get-started/getting-started-guide/schedule-your-test-runs.md).

# Schedule Your Test Runs

Testery is really flexible about when, where, and how you run your tests. To schedule your tests to run nightly for example you can,

1. Navigate to **Test Triggers** and click **Add New Trigger.**
2. Give your trigger a **Trigger Name** (e.g. "Nightly Run").
3. For Trigger Type select "Run tests on trigger" and enter a valid cron expression. For example, to run the tests every night at midnight UTC you can use the following cron expression:\
   \
   0 0 \* \* \*\
   \
   See <https://en.wikipedia.org/wiki/Cron> for more information about cron.
4. Set **Project with Tests** to the project you just set up. Here you can select what tests you want to run. For now, just pick "Run all tests in project" to run all of your tests.
5. For **Environment** select the environment you set up earlier. For example "Development".
6. Then select **Specific Version** and chose **Branch** and leave **Commit** set to "latest". This will run the latest commit for the branch.

As you can see, there's a lot of flexibility. See [Test Triggers](/get-to-know-testery/schedules.md) for more information about all the different options.


---

# 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.testery.io/get-started/getting-started-guide/schedule-your-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.