Skip to content

Browser tests, in the browser

Dyno runs your tests inside the browser, right next to your app, and plots every run as it happens.

Write your first testRead the API

An example pull

12 tests @ 2.39 s

12 tests2.39 s of test time
This pullSteep is fast. That flat stretch is one slow import test.

An example pull

12 tests @ 1.33 s

12 tests2.39 s of test time
This pullLast pull, 2.39 sThe import got faster. This pull beat the last one by 1.06 s.

Write a test the way you’d use your app: open a page, fill in a field, and check what changed. Dyno runs that JavaScript in the browser, with Interactor handling DOM interaction and waiting for the UI.

You get the browser APIs you already know and its devtools for debugging. The CLI starts your app, opens a browser, and reports the results.

Write your first test

Section titled “Write your first test”

Give Dyno your app’s command and URL, then pick one workflow to test. The setup guide walks through it. You’ll need Node 24+; Playwright Core is included.

See what happened

Section titled “See what happened”

Run dyno --ui to keep the app open. Bring up the reporter to read failures, console output, screenshots and timings. The app keeps its full viewport while you inspect it.

You can also open the test URL yourself in another browser. Browser setup explains what’s available in managed and manual runs.