Personas that persist
Keep a signed-in profile for each test account, with its own storage, ready for every run.
Use cases / QA & web testing
See your site as every user does.
QA and web teams test how a site behaves for different users, locales and devices. Browz gives each test persona its own saved profile, exit, timezone and languages, and lets you drive them all from Playwright or Puppeteer.
Browz · Test personas
The problem
Shared browsers leak between accounts.
Without separate profiles
- Clearing cookies between every test run
- Faking a locale by hand in dev tools
- Bugs that only show up in another country
- Test logins that collide with each other
With Browz
- A saved profile per persona, signed in
- Timezone, languages and screen set per profile
- An exit in each country you ship to
- Isolated storage, so test accounts never collide
How Browz helps
Built for qa & web testing.
Locale, timezone and screen
Set languages, timezone, screen size and more per profile, or let them follow the profile’s exit.
Automate with the tools you use
Start a profile from the API or CLI and connect Playwright, Puppeteer or Selenium over CDP.
Block what you don’t want
Per-profile website blocklists keep chosen hosts, such as analytics, out of test sessions.
A setup that works
Get started in an afternoon.
Create a profile per persona
One profile for each test account and locale, filed in a QA folder.
Set locale and exit
Choose languages, timezone and screen, and a proxy in the country you are testing.
Drive it from your tests
Call browz start, read the debug port, and connect your test runner over CDP.
Features you’ll use
The parts that matter here.
FAQ
Questions we hear.
Can I run Browz in CI?
Browz is a desktop app for Mac and Windows. You can drive it from tests running on the same computer through the local API.