TestingForge Browser Flows

Browser Flows · New

Real Chromium walks.
Same bill as an API run.

Login, click, wait, assert, screenshot — headless, in CI, next to your HTTP bricks. Critical UI smoke that ships with the suite you already trust. Not a second browser stack to babysit.

Start with Browser Flows Scaffold from Cursor

Successful browser run = same metered price as a successful API run.

1 meter
API + browser usage
€0
extra browser SKU
MCP
scaffold in Cursor
CI
same TF_API_KEY

What a flow actually is

An ordered checklist for headless Chromium. Each step is one browser action. The result is a normal AutomationRun — same Runs UI, same CI polling, same invoice line.

Steps people understand

Open a page, type into a field, click, wait for URL, verify text or visibility. Build in the UI or from Cursor via MCP.

Secrets stay secrets

Emails and passwords come from org options ({option.E2E_*}). No pasting credentials into step JSON for CI.

CI one-liner

start_run with browser_flow_code. Poll get_run. Same TF_API_KEY as API scenarios.

Agent path: minutes, not a week

New SPA client? Don’t invent twenty steps. Scaffold a login smoke, dry-run, fix selectors, ship.

1

Check readiness

workspace_onboard_status — browser runtime, missing E2E_* secrets, next tool to call.

2

Scaffold login smoke

workspace_scaffold_login_smoke with base URL + credentials. Stores secrets and creates the flow.

3

Dry-run, then queue

workspace_dry_run_flow → fix with workspace_update_flow → workspace_run_flow / CI start_run.

cursor · testingforge mcp 
# cheap path for a new SPA client
→ workspace_onboard_status
← ready · secrets missing: E2E_USER_PASSWORD

→ workspace_scaffold_login_smoke
← flow login_smoke created

→ workspace_dry_run_flow
← PASS  ·  6 steps  ·  12.4s

→ start_run(browser_flow_code=…)
← queued  ·  same meter as API

Browser Flows vs full E2E frameworks

We are opinionated about the slice we cover — so you don’t pay for a second platform.

Use Browser Flows when you want…

  • Login + critical path smoke next to your API suite
  • One product, one TF_API_KEY, one runs inbox
  • MCP / Cursor to scaffold and patch flows
  • Same metered billing as a successful API run
  • Screenshots and step timeline when something breaks

Keep Playwright / Cypress when you want…

  • Huge UI matrices and visual regression farms
  • Complex component testing in the frontend repo
  • Custom browser tooling your team already owns
  • Pixel-perfect multi-browser grid at massive scale

Ship UI smoke without a second stack

API bricks for contracts. Browser Flows for the walk users take. One bill, one CI key.

Create account See pricing