Testorax QA Proof Bridge av proabouzekry

Testorax QA Proof Bridge captures a small, redacted summary of the active tab — page title, visible link/button labels, viewport size, and visible-control counts — and POSTs it to your own Testorax account at https://testorax.com.

This lets Testorax verify that what its automated runner sees matches what a real Firefox/Chrome user sees ("chrome_checked" parity). It runs only on user click. There is no background scraping, no telemetry, no cross-site tracking.

What it captures (active tab only, on user click):
- Page title and final URL (secret query parameters stripped)
- Visible counts of buttons, links, dropdowns, tabs, inputs, forms
- Visible button and link text labels (capped at 60 each, 200 chars max each)
- Viewport size
- Heuristic logged-in / logged-out indicator

What it never captures:
- Cookies, Authorization headers, or any session token
- Passwords or any input field values (typed text is never read)
- localStorage or sessionStorage values
- Browsing history or background tabs
- Request or response bodies

Where the data goes:
- Only to the Testorax API base you configure (default https://testorax.com).
- Authenticated by an API key you paste into the popup once. The key is stored in browser.storage.local and is never sent anywhere except your configured Testorax base.
- No third-party analytics, no remote code, no eval.

Who this is for:
- Testorax customers who want to confirm that automated-runner output matches a real human-browser session before signing off a test report.

Source code is available on request via the support email below.