01 / The problem
What the system needs to solve
Testing a web form across browsers, devices and locations usually means juggling separate tools and reconfiguring proxies by hand for every run. QA teams need repeatable test matrices and evidence they can share, not screenshots collected ad hoc.
02 / The approach
How the pieces fit together
- Drive real browser engines (Chromium, Firefox, WebKit and installed Chrome, Edge, Brave and Opera) through Playwright from an Electron shell.
- Route each session through a location-targeted proxy by country, state, city or ZIP code and verify the exit IP before the test starts.
- Record a test scenario once, then run it as a browser × device × location matrix.
- Store proxy credentials encrypted on the local machine and give every run an isolated browser profile.
03 / Key features
What it does
- 226 device presets for mobile, tablet and desktop emulation
- Sticky and rotating proxy sessions with automatic location matching
- Screenshots, network requests, HTTP responses and form-generated IDs captured as test evidence
- Accessibility checks and performance validation inside test runs
- Cross-platform builds for Windows, Linux and macOS
04 / Results
What it delivered
- Released free and open source under the Apache 2.0 license
- Distributed for Windows, Linux and macOS
05 / The tradeoffs
Engineering is a set of choices
Real browser processes produce results that match what users see, but they are heavier than headless HTTP checks. Every run carries process lifecycle, proxy session and profile isolation costs that the app has to manage explicitly.
06 / Validation considerations
What to test before relying on it
Confirm the proxy exit location before each launch, and keep the network log and screenshots with every result so a failure can be reproduced rather than re-described.