Creating Test Cases

Test cases define the scenarios Operio executes against your environments. Create them under Tests.

Create a new test case

Open Tests in the sidebar.
Click New Test Case.
Enter a clear name and an optional description.
Choose a type:
- Structured: ordered steps the agent follows.
- Autonomous: a natural-language goal. The agent decides how to achieve and verify it.
Set a severity (critical, high, medium, or low).
Optionally assign the test to a suite, add preconditions, and apply tags.
Save as draft or Publish.

Published test cases can go into suites, runs, and monitors. Drafts sit in your library until you publish them.

Structured test cases

Structured tests are built from steps. Add steps with +, reorder them by drag and drop, and pick a type for each:

Step type	Use it to
Action	Do something: navigate, click, type, upload, and so on
Verify	Check an expected outcome, like a message, page state, or UI element
Login	Sign in with a project credential selected from a dropdown
Screenshot	Capture the current page with a label (for example `Footer` or `Checkout summary`) so you can review it in the run results
Wait	Pause for a set number of seconds (1–180, default 5) before the next step
Shared Steps	Insert a reusable sequence from your shared steps library

Write Action and Verify steps in plain language, and be specific about what to interact with and what success looks like. Vague steps make the agent guess; precise ones make results repeatable.

A structured test needs at least one step (of any type) before you can save it.

Assets

If a flow needs a file, attach a project asset (a file or image) to the step, or mention it with @ in the step text. A common case is a test that uploads a document.

Autonomous test cases

For an autonomous test, you write a goal describing the outcome you want:

Log in as @Standard User and confirm the dashboard shows the account name.

The agent plans and executes the flow at run time. Type @ in the goal to mention a credential or asset the agent should use.

Reach for autonomous tests when the path can vary but the goal is clear. When you need a fixed sequence, stick with structured tests.

Using credentials and assets

You can insert project credentials and assets in three ways:

Login step — in a structured test, add a Login step and choose a credential from the dropdown.
Mention in step text — type @ in an Action or Verify step and pick a credential or asset by label.
Mention in an autonomous goal — type @ in the goal field and pick a credential or asset the agent should use.

Credentials are project-scoped, so the same mentions and Login steps work across every environment.

Best practices

Keep each test case focused on one user flow or outcome.
Prefer shared steps for repeated setup like login, navigation, or seed data.
Use severity to flag business-critical paths.
Use Screenshot steps at key checkpoints you want to inspect later in Activity.