Guide

Authoring scenarios

A scenario is a short prose description of a user journey. Orbis turns it into clicks, types, and assertions at run time. There is no DSL to learn.

Anatomy

Every scenario has three things:

A start. The URL to open.
A flow. The actions to take, in order.
One or more assertions. What must be true at the end.

A complete example

Go to https://app.example.com/login.
Sign in as qa@example.com / hunter2.
Open the Billing page from the sidebar.
Verify that the current plan is "Free".
Click "Upgrade to Pro".
On the Stripe checkout page, fill the test card
4242 4242 4242 4242 and submit.
Wait for the success screen and confirm it shows
the text "Welcome to Pro".

Tips

Write one sentence per step. Short sentences run more reliably than long compound ones.
Name targets by what the user sees. Buttons by their label, fields by their placeholder, links by their text.
Include the explicit success condition. The agent stops on the first assertion that passes the whole journey.
If a step is dynamic, say so. e.g. "wait for the dashboard to finish loading".

Common mistakes

Referring to CSS selectors. There are none. The agent reads the page like a person does.
Skipping the success criterion. Without an assertion, the agent has nothing to confirm.
Mixing two journeys in one scenario. Split them into a suite instead.