> 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/doesqa-concepts.md).

# DoesQA concepts

DoesQA helps you test a website without writing code. You describe what a user does, DoesQA runs those steps in a real browser, and you get clear results you can trust.

## How a test is built

| Piece         | What it is                                                                                                |
| ------------- | --------------------------------------------------------------------------------------------------------- |
| **Flow**      | Your test design. One Flow can cover several routes through your application.                             |
| **Test Step** | One building block in a Flow. Each step does a single job: open a page, touch a button, or check a value. |
| **Element**   | A reusable page object, such as a login button or email field.                                            |
| **Value**     | A piece of data used in a test, such as a username or URL.                                                |

You can build a Flow in two places that share the same Test Steps:

* The [**Scenario editor**](/platform/scenario-editor.md) turns each Test Step into a plain-language sentence. New Flows open here.
* The [**Flow Builder**](/platform/flow-builder.md) shows the same Test Steps on a visual canvas. Use it when you want more power or flexibility.

AI is optional and layered. See [DoesQA AI](/platform/doesqa-ai.md).

## How a test runs

| Piece           | What it is                                                                                      |
| --------------- | ----------------------------------------------------------------------------------------------- |
| **Flow Branch** | A join or split in a Flow that creates more than one possible path.                             |
| **Test Case**   | One specific path through a Flow. Each unique path becomes its own Test Case.                   |
| **Run**         | A group of Test Cases started together.                                                         |
| **Test Runner** | A machine that runs one Test Case. More runners means more Test Cases can run at the same time. |

```mermaid
flowchart TD
  open["Open URL"] --> touch["Touch Element"]
  touch --> check["Check element displayed"]
```

A simple Flow like this produces one Test Case. Add a Flow Branch later, and DoesQA creates a Test Case for each path while shared steps stay shared. See [Choose Flow Branch shapes](/better-coverage/choose-flow-branch-shapes.md) when you are ready to design those paths.

## Related

* [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)
* [Terminology](/getting-started/terminology.md)