> 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-to-know-testery/setting-test-execution-priority.md).
# Setting Test Execution Priority
Testery enables you to set a Test Execution Priority to optimize how your test runs are queued up. When there are multiple test runs in a queued state, the test runs with the lowest numbered priority will be executed first. If you would like multiple test runs to execute at the same time, make sure that you have also [set the number of parallel tests](/get-to-know-testery/setting-the-number-of-parallel-tests.md) to a number lower than your account limit.
#### Setting Default Priority for a Pipeline Stage
To set the priority for different Pipeline Stages, navigate to `Environments` and click `Pipeline Stages`.
Here you can select a Test Execution Priority for the Pipeline Stage. When two test runs are queued up, the test run with the lowest numbered Test Execution Priority will be executed first.
#### Setting Priority for an Ad Hoc Test Run
Test Execution Priority may also be set for an individual ad hoc test run. To do this, expand `Show Advanced Options` and set the Priority for the test run.
#### Setting Priority for a Scheduled Test Run
Test Execution Priority can be set for [Schedules](/get-to-know-testery/schedules.md) as well. To do this, expand `Show Advanced Options` when creating or editing a schedule.
---
# 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-to-know-testery/setting-test-execution-priority.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.