Core Concepts
Key terms and building blocks of the Operio platform
These concepts map directly to how Operio is organized in the product. Once they click, structuring tests and scaling coverage gets much easier.
Team
A team is the top-level place where people collaborate in Operio. Projects, members, and shared settings all live under a team. Your account can belong to more than one.
Project
A project holds everything for one product or application under test: test cases, suites, environments, credentials, runs, monitors, assets, and integrations.
Switch projects with the selector in the sidebar. Most day-to-day work happens inside a selected project.
Test case
A test case describes a scenario Operio should verify. Test cases live under Tests in the sidebar, and come in two types:
- Structured: an ordered list of steps — Action, Verify, Login, Screenshot, Wait, and Shared Steps.
- Autonomous: a goal written in natural language. The agent figures out how to reach it and check it. You can
@-mention credentials and assets in the goal.
Test cases are either draft or published. You need to publish a test case before it can go into suites, runs, or monitors.
Shared steps
Shared steps are reusable sequences of action and verify steps, like a login flow or checkout setup. Define them once, then insert them into structured test cases so common flows stay consistent.
Manage them from Shared Steps in the sidebar.
Test suite
A test suite groups published test cases so you can run them together. Suites live inside Tests (left rail: All tests, each suite, and Ungrouped) and are the usual starting point for a test run or a monitor.
Environment
An environment is the target configuration for a run: primarily the base URL. The same test cases can run against staging, production, or anything else just by picking a different environment. Project credentials and assets are shared across environments.
See Environments for setup details.
Test run
A test run executes one or more published test cases against an environment. Each run records pass/fail outcomes, step details, logs, and screenshots.
Start runs from Tests — Run Suite on a suite, or Run on a single test case. The Runs page is for live progress, history, and reruns.
Monitor
A monitor runs selected published test cases on a schedule against an environment. Think hourly smoke checks or a daily regression suite.
Configure monitors under Monitors in the sidebar. See Scheduled Runs for the schedule options.