> 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

DoesQA has a small set of words that describe how tests are built and run.

For how these pieces fit together, see [DoesQA concepts](/getting-started/doesqa-concepts.md).

## Designing tests

| Term             | What it means                                                                                                                                                                  |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Flow**         | Your test design on an infinite canvas. One flow can cover several routes through your application.                                                                            |
| **Flow Builder** | The visual editor where you place and connect test steps to build a flow. See [Flow Builder](/platform/flow-builder.md).                                                       |
| **Test Step**    | One building block in a flow. Each step does a single job: open a page, touch a button, or check a value.                                                                      |
| **Step Group**   | A reusable set of test steps you can drop into any flow. Change the group once, and every flow that uses it updates.                                                           |
| **Flow Branch**  | A join or split in a flow that creates more than one possible path. See [Choose Flow Branch shapes](/better-coverage/choose-flow-branch-shapes.md).                            |
| **Element**      | A reusable page object, such as a login button or email field. Test steps use elements to find things on the page.                                                             |
| **Selector**     | The rule inside an element that finds it on the page, using CSS, XPath, visible text, or a test ID. The element and the selector are related, but they are not the same thing. |
| **Value**        | A piece of data used in a test, such as a username, URL, or order number. Think of it as a variable with a clear name.                                                         |
| **Value Store**  | Where your account keeps shared values, so many tests can reuse the same data.                                                                                                 |

## Running tests

| Term            | What it means                                                                                           |
| --------------- | ------------------------------------------------------------------------------------------------------- |
| **Test Case**   | One specific path through a flow. A flow with branches produces a test case for each path.              |
| **Run**         | A group of test cases started together.                                                                 |
| **Test Runner** | A machine that runs one test case. More runners means more tests can run at the same time.              |
| **Test Pack**   | A run you start yourself, choosing which flows and test cases to include.                               |
| **Run Recipe**  | A saved set of filters and value overwrites you can reuse. Find these under **Settings → Run Recipes**. |
| **Schedule**    | A recurring run. It can target all flows, flows with certain tags, or a run recipe.                     |

## Other ways to work

| Term                 | What it means                                                                                                                                                                         |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Scenario editor**  | A plain-language editor for supported single-path flows. Useful when you prefer writing steps as sentences. New Flows open here. See [Scenario editor](/platform/scenario-editor.md). |
| **Assistant**        | DoesQA's in-app AI for questions about your Flows, Runs, and coverage. See [DoesQA AI](/platform/doesqa-ai.md).                                                                       |
| **Simulated Device** | An Open option that runs the Test Case with a named device preset, such as an iPhone. It sets viewport, user agent, and touch behaviour for that device.                              |

## Related

* [DoesQA concepts](/getting-started/doesqa-concepts.md)
* [Create and run your first Flow](/getting-started/create-and-run-your-first-flow.md)
* [Understand your results](/getting-started/understand-your-results.md)
* [DoesQA AI](/platform/doesqa-ai.md)
* [Flow Builder](/platform/flow-builder.md)
* [Choose Flow Branch shapes](/better-coverage/choose-flow-branch-shapes.md)
* [Scenario editor](/platform/scenario-editor.md)
* [Reuse steps with Step Groups](/better-coverage/reuse-steps-with-step-groups.md)
* [Value Store](/values/value-store.md)
* [Run Recipes](/configuration/run-recipes.md)