Automate UI tests

Command: /ui-aqa-flow · ← All scenarios · User guide

Turn a test case into a working automated UI/browser test that follows your repo’s existing page objects and conventions — and help you get it green.

Use this when you need UI, browser, or end-to-end automation: page objects, selectors, implementing a UI test, or fixing a failing one (Playwright, Cypress, Selenium, and similar).

Not for: backend API tests (Automate API tests) or designing test cases without code (Generate test cases).

Running it

/ui-aqa-flow Automate the test case for the checkout flow
/ui-aqa-flow Add E2E Playwright tests for the dashboard
/ui-aqa-flow Fix the failing UI test for user registration

How it works

The defining rule: it never guesses selectors, flows, or data. It reads your frontend code to find selectors, and if it can’t, it asks you for the page source. You run the test; it analyzes the report and proposes fixes for your approval.

flowchart TB
    Start(["/ui-aqa-flow + test case"]) --> Collect["Collect test case + context"]
    Collect --> G1{"You answer <br>clarifying questions"}
    G1 --> Analyze["Analyze code & page objects"]
    Analyze --> Feas{"Feature & elements <br>actually exist?"}
    Feas -->|no| Stop(["Hard stop — <br>you choose how to proceed"])
    Feas -->|yes| Sel{"Selectors <br>found in code?"}
    Sel -->|no| Ask["You provide <br>page source"]
    Ask --> Impl["Implement page objects + test"]
    Sel -->|yes| Impl
    Impl --> Run["You run the test <br>& share the report"]
    Run --> Pass{"Test passes?"}
    Pass -->|yes| Done(["Passing UI test"])
    Pass -->|no| Root["Root-cause the failures"]
    Root --> G2{"You approve <br>the fixes"}
    G2 -->|refine| Root
    G2 -->|approve| Impl

    classDef step fill:#dae8ff,stroke:#3674b5,color:#102a43;
    classDef gate fill:#fff2cc,stroke:#b58b00,color:#493800;
    classDef done fill:#e5f7e8,stroke:#35834a,color:#153b20;
    classDef halt fill:#ffe0e0,stroke:#b54040,color:#5a1a1a;
    class Collect,Analyze,Ask,Impl,Run,Root step;
    class G1,Feas,Sel,Pass,G2 gate;
    class Start,Done done;
    class Stop halt;

It reuses your existing page objects and helpers before creating new ones, and every assertion traces back to a requirement. If the feature or elements simply don’t exist yet, it stops rather than inventing them — and offers you options (point it at the real feature, author the missing UI as a separate task, mark the test pending, or abort).

What you’ll be asked to do

Answer clarifying questions about assertions and behavior; provide page source if selectors can’t be found in code; run the test yourself and share the actual results/report (the agent stops and waits — it won’t fake a run); and give explicit approval before any fixes are applied.

What it creates

A plan folder plans/ui-aqa-<test-name>/ with test-plan.md (including the explicit assertions), code-analysis.md, page-sources/ (captured page HTML) and failure-analysis.md (the root-cause write-up); the implemented/updated page-object and test files in your repo; and progress tracked in agents/TEMP/<feature>/ui-aqa-state.md, which is not committed.

Generate test cases to design the case first · Automate API tests for backend tests · unsure which? use the /aqa-flow router.

Sources