Run QA and inspect its evidence on your computer
Understand the installed runtime, stored results, and preparation needed for local QA.
From installation to execution
The directly distributed reopt QA app includes its execution engine and browser runtime. You can prepare tests and inspect results without installing a separate execution server. Local automation currently uses the directly distributed macOS app.
Your service still needs a URL, test accounts, and intended outcomes. AI generation and investigation also need model provider authentication.
Separate projects and their evidence
Create separate projects for the services you manage. Keep staging and production distinct, and check account and browser conditions before a run.
Inspect reports alongside collected screenshots, logs, and traces. Identify where actual behavior diverged from the expected result, then fix and rerun.
Local storage and external connections
Execution records are stored on your computer. Testing an external site communicates with that service, and AI tasks may send required code, page content, or failure records to a model provider.
Local installation does not mean that every feature avoids external transmission. Review connection boundaries and check exported reports for sensitive content before sharing.
