Core concepts
The terms used in Operio and how they fit together.
A team contains projects. Each project holds its tests, test accounts, runs, and integrations.
| Term | Meaning |
|---|---|
| Team | The people and shared settings for a workspace. Your account can belong to multiple teams. |
| Project | Tests and resources for one application. Choose web or mobile when creating it. |
| Test case | A saved scenario with ordered Action, Verify, Login, Screenshot, or Wait steps. Publish it before running it. |
| Test suite | A group of test cases you run together. Manage suites under Tests. |
| Environment | A web target's base URL, such as staging or production. |
| Build | The uploaded iOS or Android binary selected for a mobile run. |
| Run | An execution of tests against one environment or build, with results and evidence. An exploratory run executes a one-off goal. |
| Schedule | Runs a suite on a time schedule with its current test cases, against an environment (web) or the latest ready build (mobile). |
Test accounts and assets belong to the project and are shared across its run targets.
Test lifecycle
Write a draft, review its steps, then publish it. Published tests can run individually or as part of a suite. Review execution history under Runs.
In the CLI and API, published tests use the status active. Deactivating a test makes it inactive and excludes it from runs without deleting it.
Continue with writing a test or running tests.