Skip to content

DOCS · QUICKSTART

One journey. One observable result.

Set up a short flow in a controlled environment, replay it locally and inspect the evidence before expanding coverage.

  • 15-minute path
  • Controlled environment
  • Privacy review first

DOCS / GETTING STARTED

FIRST RUN

Ready before broad coverage.

  1. 01

    Choose one critical journey

  2. 02

    Authorize the exact origin

  3. 03

    End with an assertion

  4. 04

    Review the evidence set

SMALL SCOPE CLEAR OUTCOME
READY First deterministic replay
15 MIN
VERSION Desktop · current packaged build SCOPE macOS · Apple silicon · local runtime

OPERATING GUIDE

Controls are named exactly as they appear in the current desktop application for the selected interface language.

01 · BEFORE OPENING

Pick a stable environment. Define success in one sentence.

Use a test or staging environment the Mac can reach. Decide the visible state that proves the journey completed before authoring any steps.

  1. 1.1
    JOURNEY

    Keep the first path short

    Sign in, create a test record or reach a checkout review state in three to eight steps.

    One purpose only
  2. 1.2
    DATA

    Use dedicated test values

    Do not begin with production customer data. Decide credential and evidence handling before the run.

    Review local policy

02 · AUTHOR

Authorize one origin. Approve the proposed flow.

Open the target site, fix the permitted origin and create the journey by recording actions or describing the expected result to the integrated agent.

  1. 2.1
    CREDENTIALS

    Store references, not prompt text

    Keep credentials encrypted locally and let the runtime fill them by reference.

    Local fill
  2. 2.2
    ASSERTION

    Finish with something visible

    Add an exact, observable condition that distinguishes completion from mere navigation.

    Required for useful replay

03 · VERIFY

Run it unchanged. Read the evidence once.

Replay the flow locally. Confirm step ordering, final assertion and privacy-mode artifacts while the baseline is still known to be correct.

  1. 3.1
    PASS

    Confirm the clean baseline

    A passing run proves the journey is configured; it does not by itself prove every application state.

    Record the run ID
  2. 3.2
    REVIEW

    Open the artifact manifest

    Check that the evidence is useful and that expected sensitive regions are masked.

    Before scaling coverage Privacy checklist

Integrated desktop QA agent

Describe it once. Replay it deterministically.

The integrated agent authors the journey inside the site you authorize. Later runs replay that deterministic flow and keep the redacted evidence on the Mac your team controls.

macOS · Apple silicon · Signed device entitlements