> For the complete documentation index, see [llms.txt](https://docs.does.qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.does.qa/getting-started/terminology.md).

# Terminology

<table><thead><tr><th width="214.421875">Term</th><th></th></tr></thead><tbody><tr><td>Flow</td><td>Your Flow is a infinite canvas where you can design your tests.</td></tr><tr><td>Branch</td><td>Branches is when your Flow has multiple possible routes.</td></tr><tr><td>Test Case</td><td>A Test Case is a specific and unique route through a Flow.</td></tr><tr><td>Run</td><td>A Run is a collection of Test Cases started together.</td></tr><tr><td>Test Runner</td><td><p>A Test Runner executes your test cases. The number of runners you have determines how many test cases can run simultaneously.</p><p><br>For example, if you have 20 runners, up to 20 test cases can run in parallel. As each test case finishes, the next one in the queue starts automatically.</p></td></tr></tbody></table>


---

# 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:

```
GET https://docs.does.qa/getting-started/terminology.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.