Proxy QA Browser documentation

What Proxy QA Browser is: a free, open-source desktop app for testing your own web forms by location, on emulated devices and in real browsers.

Download and run Proxy QA Browser on Windows 10 and 11 (portable EXE), Linux (AppImage) and macOS 12+ (DMG): first launch, moving and uninstalling.

The first-run set-up wizard: bundled browsers, optional proxy keys stored in the encrypted vault, the Manage keys window and a tour of the main window.

Launch Chrome, Edge, Brave or a bundled engine for QA through a built-in proxy provider or directly, in a fresh profile, with the exit IP checked first.

Bring your own plan from a supported proxy provider: logins, location targeting by provider and sticky or rotating sessions. Not affiliated with any provider.

Target a country or a US state, city or ZIP, check the exit IP's reported location before the window opens, and emulate phone, tablet and desktop presets.

Bundled Chromium, Firefox and WebKit plus installed Chrome, Edge, Brave and Opera: one-click installs, detection without starting them, and known limits.

Send a secret header only to origins you list, so your own staging WAF or CAPTCHA can allow QA traffic and your form backend can tag it as test leads.

How signed online and USB updates are verified with Ed25519 and SHA-256, the computer copy, the startup update check and updating on macOS.

Record QA scenarios, import CSV datasets, run browser × device × location matrices, compare screenshots, schedule runs and export JSON, JUnit or HTML.

Check consent disclosures and checkboxes, lead-certificate scripts (TrustedForm, Jornaya LeadiD), axe-core accessibility rules and performance budgets.

How self-healing selectors keep recorded tests running when an id or class changes: up to four fallback locators, flagged in results, warn or fail modes.

Run exported scenarios and suites headless in CI with the command-line runner, the Docker image or the GitHub Action, with JSON, JUnit and HTML reports.

Connect Claude Code, Cursor or another MCP client so an AI assistant can run geo- and device-aware QA checks, with navigation limited to origins you allow.

The AES-256-GCM credential vault and OS keychain, what is never logged, Electron hardening, every network connection the app makes and where data is stored.

Reference for every Proxy QA Browser setting: where it lives, its default and allowed range, QA automation policy limits and environment variables.

Fix common problems with installing, proxies and locations, browsers, sessions, the vault and QA automation, and look up what each error code means.

Answers to common questions about Proxy QA Browser: cost, responsible use, data and privacy, proxy plans, browsers, emulated devices, CI and AI assistants.

How Proxy QA Browser is built: the Electron process model and IPC contracts, source layout, start-up, a launch step by step, providers, data and security.

Set up a development environment, run the tests, follow the code conventions and project scope, add a proxy provider and open a pull request.

Build the Windows EXE, Linux AppImage and macOS DMG, sign update manifests with Ed25519, publish tagged releases through CI and deploy the website.