# From acceptance criteria to QA sign-off

Turn a spec's acceptance criteria into checks, prove them in the built-in browser, report bugs and sign the work off.

Lena, Northwind's PM, wrote the acceptance criteria for "Keep the cart across devices". Dan built it and opened a pull
request with a preview link. Adam, in QA, now proves each criterion and signs the work off. This page follows Adam.

Before you start:

> **Desktop app only**
>
> The built-in browser, recordings and proof capture run in the desktop app. Teammates read attached proof on the web.

- Your org needs the `browser` module. EasyCode staff can stop the built-in browser with the [`browser`](/reference/kill-switches-and-modules#browser) kill switch.
- You need a task on the product, and a page to test: a preview, a staging link or the app running locally.

## Walk it through

### Read the criteria on the task

Open the task and its **Documents**. A **Spec** document starts with an _Acceptance criteria_ section; that list is
what you test. If a criterion is vague, comment on its block and ask Lena before you start. See
[Write a spec with your team](/guides/write-a-spec).

### Turn the criteria into a test plan

Start a session on the task with **Start task**. If your org's kit has the QA role pack, the agent has the **Write a
test plan** skill: every criterion gets at least one case, with its setup, steps, expected result and data. Ask for
it, and keep the plan as a document on the task so the team can review it. See
[Start a session](/guides/start-a-session).

### Open the page in the browser pane

In the session, open **Browser**, then **Open a page**, and paste the preview address. The pane sits beside the
chat. **Tools** sets the **Device size** and the **Browser profile**, so sign-ins stay in this workspace.

The first time the agent wants to use a site, a bar asks you. Choose **Allow this time**, **Always allow here** or
**Don't allow**. You can stop the agent at any time.

### Have the agent prove each criterion

Ask the agent to check each criterion as a flow, for example "add an item on one device, sign in on another, the
cart still holds it". It drives the page while you watch, and saves the result as proof with [`proof_run`](/reference/mcp-tools#proof-run).

Open **Proof** in the session. Each proof card lists its flows, each marked Passed or Failed, with the stills and
the page's errors, failed requests and warnings.

### Look over the proof before it is shared

A card shows where its proof stands:

- **Attached**: it is on the workflow run, for the team to see.
- **Held**: "Held on this computer. Look it over first. Nothing is attached until you say so." Press **Attach
  anyway** once you have checked it.
- **On this computer**: the session is private, so nothing is uploaded.

**Copy PR block** copies the proof's summary for the pull request's description. **Run again** repeats the checks.

### Record what you see

Some checks need a person's eye. Open **Tools**, then **Start recording**, and use the page. Private details on the
page are covered while it records; typed text is never shown. Press **Stop recording** when you are done. The
recording lands in **Proof** as a card made by you.

To point at a problem, press **Pick an element**, click a part of the page or drag over an area, and write a note on
each. **Send 2 notes** (the count follows yours) passes them to the agent.

### Report a bug

On a proof card you made, **Report a bug** builds the report: the steps in EasyCode's words, your comments, and the
page text marked separately. Then:

- **Send to agent** adds it to your message, so the agent can fix it in this session.
- **Create bug** prepares a bug task on the product; check it and press **File bug**.
- **Copy report** copies the text for anywhere else.

### Sign it off at the gate

EasyCode has no separate QA button: sign-off is a gate in your team's workflow. In **Ship a feature**, the **Approve
the change** gate shows the diff. Its approver reads the proof attached to the run and presses **Approve**, or
**Request changes** with what to change. **Reject** stops the run. A workflow author can add a gate of their own for QA in the workflow editor. See
[Workflows, gates and the board](/guides/workflows-and-the-board).

## Where does the team see the proof?

Attached proof shows in the session's **Proof** on the web too, so Lena and Dan can read it without the desktop app.
When the agent adds the proof block to the pull request, reviewers on GitHub see it too. When the pull request merges, the task moves to **Done** on the board.

## Related

- [Test in the built-in browser](/guides/browser-testing)
- [Test a staging link in the built-in browser](/walkthroughs/browser-qa)
- [From idea to merged PR](/scenarios/idea-to-merged-pr)
