USE CASE · QA TESTING

QA runs are easier to trust when you can see the browser.

Remote Browser gives QA scripts and agentic test harnesses a visible, controllable Chromium session with screenshots, recordings, profile state, and CDP automation.

Start a QA browser Read Playwright docs

qa-test.tsremote

const page = browser.contexts()[0]!.pages()[0]!;
await page.goto("https://app.example.com/login");
await page.getByLabel("Email").fill(process.env.QA_EMAIL!);
await page.getByRole("button", { name: "Sign in" }).click();
await page.screenshot({ path: "reports/login-final.png" });

headedvisible browser

profileauth reuse

recordingrun evidence

Agentic UI testing

Let a local coding agent drive a visible browser, collect screenshots, judge expectations, and produce repeatable reports.

Authenticated workflows

Profiles help tests start from prepared accounts instead of rebuilding login state every time.

Debuggable failures

When a test fails, open the live viewer or recording to see what the user-facing page actually did.

Workflow

From browser creation to evidence.

Prepare

Use APIs for test setup where possible, then reserve the browser for the user-facing workflow.

Run

Drive UI steps through Playwright, Puppeteer, or an agent connected to the remote browser.

Classify

Use screenshots and recordings to separate harness failures, unclear test cases, and real product defects.

FAQ

Short answers for searchers and AI crawlers.

Is this meant to replace all CI tests?

No. Keep deterministic CI tests. Use Remote Browser when visibility, auth state, screenshots, or agent judgment matter.

Can developers watch a test as it runs?

Yes. The live viewer is built for observing browser state while automation is active.

Can it work with spreadsheet-based test cases?

Yes. A harness can read test cases from files, drive Remote Browser, and write screenshot-rich reports.

Keep moving through the browser automation map.