# Automated QA

> Browser replays and smoke gates that check every change before and after publish.

QA is the part of Automo that tests your app for you. It runs on changes, before publish and after, so what reaches production has already been exercised.

## What QA does

- **Deterministic browser replays.** Key journeys, such as signing in or checking out, are replayed step by step in a real browser.
- **Self-healing tests.** When a harmless change moves a button or renames a selector, tests adapt instead of failing for no reason.
- **Smoke gates before publish.** If a core journey breaks, publishing is held until it is fixed.
- **Production checks after publish.** The live app is checked again once it ships.

## Telling QA what matters

Describe your critical journeys in plain language: "a customer can book a session and receives a confirmation." Those are the flows worth protecting first.

## When a check fails

You get a description of the step that failed. Ask the builder to fix it in the chat, then let QA run again.

> [!note] Automated tests complement your own pass, they do not replace it. See [Testing your app](/build/testing-your-app).

Next: [Security scanning](/build/security-scanning).