Test Cases

A Test Case is the unit of testing in Auretis, one scenario inside a test suite. A good test case reads like a short story about one user goal ("a returning customer signs in and sees their dashboard"), not a grab-bag of unrelated checks.

Two kinds of test case

You author a case in one of two styles:

• Simple: describe the whole goal as a single plain-language task, and the web agent works out how to carry it out. Fastest to write, best for straightforward flows.
• Advanced: compose explicit, ordered steps in the step builder (locate an element, act on it, assert on it). More control, and failures point to the exact step or assertion. Best for detailed or fragile flows.

Both kinds start from a URL, run on a real browser, and produce an execution.

Settings every case shares

• Start From URL (optional): where this case begins. Defaults to the suite's Start From URL. Set it to override for this one case.
• Custom instructions (optional): standing hints for the agent that apply to the whole case, e.g. "dismiss the cookie banner before doing anything." Use them for context, not for restating the task.
• Agent capabilities: what the agent may do beyond interacting with the page. Scrolling (on by default), navigation (address bar, back/forward, reload), and tab management (off by default). On a Simple case these are set on the case. On an Advanced case they're set per step. See Steps & the Step Builder.

Assertions make it a test

A case with no check can run, but it can't fail meaningfully, so every case should assert something. In a Simple case you phrase the check in plain language. In an Advanced case you add an explicit assertion step.

Go to /login, sign in as the demo user, and confirm the page lands on
/dashboard with the heading "Welcome back" visible.

Where test cases live

The full chain, top to bottom: project → regression → test suite → test case. When you run a case, or any level above it, Auretis records the run as an execution.

Next