Browser tests

A Browser test drives a real browser through your app instead of sending raw HTTP requests — page timings, Web Vitals, screenshots, and full session capture for every browser instance.

Create a browser test

From Tests → New test, select the Browser test card, then choose how to author it:

1. Upload script — bring a scenario for any browser-capable executor. The two first-class choices are a Selenium .py script (or Selenium IDE .side project) and a Playwright script; WebdriverIO specs are also supported.

2. Scriptless builder — compose the browser steps directly in the console: navigate, click, type, wait, assert, and more, with no code. See Scriptless test builders.

One browser, one pass

The scriptless builder also offers a browser-functional load seed — one browser running one iteration — for teams that want to verify a flow works rather than load-test it. It’s the browser equivalent of a functional API test.

What gets captured

Capture is automatic — you don’t edit your script, add logging, or configure a proxy. For every browser instance in the run, MaxoPerf records:

• Video — a clean recording of the browser (no “controlled by automated test software” infobar).
• Steps — the ordered actions the test took (navigate, find element, click, type, …), timestamped and synced to the video.
• HAR — the full network waterfall (requests, responses, status, size, timing).
• Console — the browser console output (logs, warnings, errors).

Capability	Chrome / Chromium	Firefox
Video	✅	✅
Steps	✅	✅
Network HAR	✅	Roadmap (WebDriver BiDi)
Console logs	✅	Roadmap (WebDriver BiDi)

See Record browser tests — video, steps, HAR & console for how to read the captured session on a run.

Bring your own browser grid

If you already have a Selenium or Playwright suite and want to point it at MaxoPerf-hosted browsers directly — outside the test/run model, with your own test runner and CI — that’s what Browser fleets is for: one central endpoint that speaks WebDriver and Playwright connect(), with the same video/steps/HAR/console capture.

Browser fleets A managed Selenium Grid & Playwright endpoint — drop-in for your existing suite.

Where to go next

Scriptless builders Point-and-click step authoring — navigation, interaction, waits, assertions, and control flow.

Executors Every browser-capable executor MaxoPerf supports.

Performance tests When the load is raw HTTP instead of a real browser.