Installing the QA extension
The Repave QA extension lets testers pin problems on your staging site and send them to Repave (see Bug reports). It works in Chrome and Edge. Your Repave server hosts it, so it installs without the Chrome Web Store, including on networks with no internet access.
A browser installs an extension from outside its store only when a policy allows it, so your IT admin sets one of the two policies below, once. IT setup on Bug Reports shows both, already filled in with your server's address and the extension's ID.
Install it for everyone
Testers do nothing; the extension appears in their browser.
| Policy | Value |
|---|---|
ExtensionInstallForcelist | <extension id>;https://<your repave server>/api/cli/qa-extension/updates.xml |
Which sites it may use
The extension asks once for access to the sites a tester visits: browsers take a screenshot for an
extension only when it has that. To grant it without the prompt, or to keep the extension to your
staging sites only, set ExtensionSettings for the extension's ID: runtime_allowed_hosts lists the
sites it may use (your staging hosts and your Repave server), and runtime_blocked_hosts set to
*://* blocks everything else.
Let testers install it from Repave
Testers click Install QA extension on Bug Reports and confirm the browser's prompt.
| Policy | Value |
|---|---|
ExtensionInstallSources | https://<your repave server>/* |
ExtensionInstallAllowlist | <extension id> |
Chrome and Edge
The policy names are the same in both browsers; each reads them from its own policy location (Group Policy, the registry, a configuration profile on macOS, or a JSON file on Linux).
Updates
The extension has its own version. Upgrading Repave does not reinstall it unless the extension itself changed.
When a Repave upgrade needs a newer extension, the extension says This Repave server needs Repave
QA
- installed by policy: updates at once (the browser would otherwise pick it up within a few hours);
- installed from Install QA extension: opens the new package, and the browser asks to add it;
- loaded unpacked: downloads the new build. Unzip it over the old folder, then click Reload on
Repave QA in
chrome://extensions.
Staging builds
For reports to say which build they were seen on, set REPAVE_BUILD_INFO=true in your staging
deployment's environment. See Bug reports.