> 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/understand-your-results.md).

# Understand your results

After you select **Run**, DoesQA opens the Flow's **Results** tab. This is where you watch the Run and decide what to change next.

For account-wide history, Test Packs, Recipes, and reruns, see [Runs](/runs/runs.md).

## What you see while it runs

Each Test Case moves through **Queued**, **Creating Runner**, and **Running**. The Run shows:

* the Run ID
* when it was created
* each Test Case card
* the browser, such as **Chrome (Desktop)**
* progress through the Test Steps

Open a Test Case to see the step timeline. Each step can show its status, a screenshot, when it started, and how long it took. When the Run finishes, you can also review the video.

## How to read a failure

Start with the first Test Step that did not pass.

1. Open that Test Case.
2. Find the failing Test Step in the timeline.
3. View the screenshot and the step response.
4. Go back to the **Scenario** or **Flow** tab and adjust that step.

A failed **Check address** usually means the Open URL or the expected value needs updating. A failed **Check title** usually means the page did not load the way you expected.

## What to do next

Once one Flow is passing:

* Add more Checks or Actions for the journey you care about.
* Switch to the **Flow** tab when you want branches or a visual layout.
* Start a **Test Pack** from the Flows list when you want to run several Flows together.
* Set up a **Schedule** when the same Run should happen regularly.

## Related

* [Create and run your first Flow](/getting-started/create-and-run-your-first-flow.md)
* [DoesQA concepts](/getting-started/doesqa-concepts.md)
* [Terminology](/getting-started/terminology.md)
* [Schedules](/configuration/schedules.md)