1 item
Capture redacted Chrome evidence for Testorax QA parity. Testorax Chrome Proof Bridge is a companion extension for Testorax that captures redacted Chrome evidence from the active tab for a specific Testorax QA preview job. It helps Testorax compare what its automated runner sees against what a real Chrome browser sees. This allows Testorax to confirm Chrome parity, detect runner-vs-Chrome mismatch, and avoid falsely reporting runner/environment issues as app bugs. What it does: - Captures visible QA evidence from the active Chrome tab - Counts visible buttons, links, forms, tabs, dropdowns, and basic page controls - Sends redacted evidence to Testorax for a specific preview job - Helps Testorax produce a chrome_checked parity result when real Chrome evidence exists - Helps developers and AI coding agents verify whether a finding matches real Chrome behavior What it does not collect: - Cookies - Passwords - Tokens - Authorization headers - localStorage or sessionStorage values - Browsing history - Raw request or response bodies - Credit card data - Full page HTML - Background browsing activity The extension only captures evidence when the user triggers capture for a specific Testorax job. It is designed for QA proof, browser parity verification, and safe evidence collection. Testorax Chrome Proof Bridge is intended for developers, founders, QA operators, and AI-assisted development workflows using tools such as Claude Code, Cursor, Codex, and other coding agents. This extension requires a Testorax account or API key to submit evidence to Testorax.
May 7, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.