Skip to main content
The Scout you send determines the quality of the intel you receive. Personas and scopes work together to emulate real situations and uncover issues traditional automation rarely touches.

​
Personas

Ideal for onboarding flows. Scout prioritizes discoverability, broken entry points, and confusing copy.
Tune each persona with:
  • Voice & tone – Describe how the persona thinks (“cautious newcomer”, “impatient hacker”).
  • Goals – Outline must-complete tasks or success criteria.
  • Forbidden paths – Anything the persona should avoid, like deleting production data.

​
Scopes

Scopes define the playground for an exploration.
​
Environment
url
required
Provide the URL or deep link where the persona should begin.
​
Entry point
string
Tell Scout whether to start authenticated, as a guest, or by completing a setup action first.
​
Timebox
duration
How long the persona should explore before handing back the report.

​
Mission templates

Reuse combinations of personas and scopes to maintain consistency:

Launch smoke

5-minute runs in production to validate sign-up, settings, and sign-out flows on every deploy.

Checkout deep dive

Adversarial persona on staging pushing discount logic, refunds, and failed payments.

Growth experiment

Power user persona verifying AI-generated features before you roll them to beta users.

Security sweep

Adversarial persona exploring admin surfaces and permission boundaries after major refactors.

​
Tips for crisp intel

  • Share screenshots or Looms when launching a new scope so Scout learns intent faster.
  • Keep mission templates short—multiple focused runs beat one overloaded brief.
  • Revisit persona notes monthly as your product, user base, and risk tolerance evolve.
Need a custom persona for your team? Email support@scoutqa.ai and we’ll help you craft it.
⌘I