Run a complete beta test

Test activation, evidence, plan boundaries, recovery, devices, and support quality.

01

Test a clean activation path

Create a fresh account, add one safe site, connect only the data you can verify, run a baseline, and reach the first affected URL. Record friction, unclear language, and the first moment the product becomes useful.

02

Test permission and plan boundaries

Open locked pages, attempt direct actions, and confirm that restricted runs do not call providers. Repeat key work as owner, admin, member, and viewer when those roles are in scope.

03

Test recovery

Interrupt a crawl, disconnect an integration, retry a failed tool, revisit skipped onboarding, reset a password, and open an older saved thread. The expected state and recovery action should remain clear.

04

Send actionable feedback

Include page, device class, viewport, browser, local time, steps, expected result, actual result, and a screenshot when helpful. Remove private customer data and all credentials.

Apply the guideReturn to the evidence and complete one verifiable action.
Open the app ↗
Did this guide solve the task?No account or workspace data is recorded here.