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

# DoesQA AI

## About DoesQA AI

DoesQA AI provides optional efficiency benefits across the product: faster failure triage, quicker Element setup, clearer next steps for coverage, in-product answers, and agent-driven authoring when you want it.

DoesQA was built to be easy **without** AI, so every Flow, Element, and Run still works with no AI features at all. DoesQA AI defaults to **On** for new accounts so those benefits are ready from day one. You can turn it off any time. See [Control](#control).

### Your data stays with DoesQA

* Models and data used for DoesQA AI stay **inside DoesQA**.
* Nothing leaves our ecosystem for DoesQA AI.
* DoesQA AI is hosted in our **UK datacentre**.

### How learning works

Learning is optional. When enabled, DoesQA AI gets sharper for you and for everyone on your account, so summaries, Suggestions, and the Assistant stay closer to how your team already tests.

When something useful applies more widely, other customers only benefit from **generic** learning, not from your private account detail.

| Learning         | Who it helps                                                        |
| ---------------- | ------------------------------------------------------------------- |
| **You**          | Notes and context that stay with how you work                       |
| **Your account** | Shared across everyone on that account                              |
| **Generic**      | Broad improvements that do not expose your account’s private detail |

You can opt out of Learning under [Control](#control).

## Layers

Each layer unlocks a different kind of speed. Use one, several, or all of them.

### Test and Run summaries

When a Test Case or Run fails, DoesQA can show an **AI Summary** on the result: a short title and a clear write-up of what went wrong and what to try next. Open **Assistant** from the summary to continue in chat with that failure already in context. Triage moves from scanning every step response and screenshot to reading the summary, then acting, so failure review stays short as suites grow.

![Failed Test Case with AI Summary and Assistant](https://static.does.qa/assets/ui/light/working-test-failed.png)

### Automatic element selection

When you create an [Element](/elements/creating-elements.md), set **Element configuration** to **Automatic** and write a plain-language **Description**, such as `Yellow login button in the top right`. DoesQA generates the Selector from that Description. You can switch to **Manual** later to edit the Selector yourself.

Describe the control the way a tester sees it, and DoesQA turns that into a Selector. First Flows land sooner, and when the page shifts you can refresh from the Description instead of rebuilding the Selector from scratch.

Your first Flow already uses this path. See [Create and run your first Flow](/getting-started/create-and-run-your-first-flow.md) and [Creating Elements](/elements/creating-elements.md).

### Suggestions

On the home page, DoesQA can show **Suggestions**: short ideas for what to improve next, such as coverage to add or Selectors to harden. Open **Assistant** from a suggestion, or use **Expand coverage**, to turn the idea into a guided chat. Suggestions pull practical work from how your account already tests, so your next move is already on the table and expanding coverage takes less planning time.

### Assistant

The [**Assistant**](/getting-started/terminology.md) is DoesQA’s in-app AI for questions about your Flows, Runs, and coverage. Open it from the main menu, or from a Flow, Test Case, or Run so the chat already knows what you are looking at. From home you can start topics such as expand coverage, get help, or ask anything.

The Assistant works with your account’s real context: the Flow or Run you opened from, how your team already tests, and the failures in front of you. Ask it to explain a failure, harden Selectors, or expand coverage, and it answers inside DoesQA with that context already loaded.

### CLI and MCP

The DoesQA **CLI** and **MCP** connect an AI coding agent to your account. The agent can create and update Flows and Elements, start Runs, read Test and Run summaries, and work from account memory, while you review each change in the DoesQA app. Authoring and triage happen beside the code you already ship: agents draft and adjust tests, and you stay in control with a review link for every change.

## Control

DoesQA AI is powerful but fully optional. All of DoesQA keeps working with DoesQA AI off: Flows, Manual Elements, Runs, and results stay fully usable.

**Automation Intelligence** is the account switch for summaries, Suggestions, and the Assistant. It defaults to **On** for new accounts.

To change it:

1. Open **Settings**.
2. Find **Automation Intelligence**.
3. Set **Enable Automation Intelligence** to **On** or **Off**.

**Automation Intelligence Learning** is also optional. Leave it on so Intelligence learns from your account and stays closer to how you test.

## Related

* [Flow Builder](/platform/flow-builder.md)
* [Scenario editor](/platform/scenario-editor.md)
* [Security](/platform/security.md)
* [Creating Elements](/elements/creating-elements.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)
* [AI Vision](/test-steps/vision/ai-vision.md)
* [Add visual checks](/better-coverage/add-visual-checks.md)
* [Terminology](/getting-started/terminology.md)