Quickstart
Create a plan, run it against a target environment, and review the evidence.
This guide gets you from a product journey to a reviewed Autonomy run. Start with one narrow flow, such as signup, checkout, invite acceptance, or password reset. After the first run is reliable, attach it to pull requests or release workflows.
Before you begin
You need
- An Autonomy organization with permission to create plans and runs.
- A target URL, staging environment, preview deployment, or mobile artifact.
- Test credentials or an inbox strategy if the journey requires authentication.
- A small user journey that has an obvious pass or fail outcome.
1. Create a plan
Write the plan in the language a product reviewer would use. Keep it specific enough to verify the outcome, but avoid baking in implementation details that will change with the UI.
For example:
- Create a new account with email OTP.
- Add the starter subscription to checkout.
- Confirm the receipt email arrives.
- Verify the account shows the paid entitlement.
2. Run against a real target
Run the plan against the same surface a user or reviewer would open: a preview deployment, staging app, local tunnel, or uploaded mobile build. Use the first run to confirm access, test data, and the expected end state before adding automation.
3. Review the evidence
Open the run evidence and check the summary first. If the run failed, use the failing step, replay, screenshots, network details, inbox messages, and generated checks to decide whether the issue is product behavior, environment setup, or test data.
4. Automate the useful path
After one run is stable, connect it to pull requests or release checks. Keep the first automated plan small. Add broader flows after the team trusts the evidence format and failure routing.