TestOwl Glossary: Key Terms Explained

Your workspace in TestOwl. A project contains your test suites, test cases, flows, environments, variables, secrets, schedules, team members, run history, and its own plan. See Creating a Project.

A collection of related test cases used to organise your automated tests. See Test Suites.

A runnable automated test made up of one or more steps. See Test Cases.

A reusable sequence of steps that can be shared across multiple test cases or other flows. Build it once, maintain it in one place, and every test that references it uses the latest version. See Flows.

Step <a id="step"></a>

An individual action, assertion, wait condition, or control flow operation that makes up a test case or flow. See The Step Editor and the Step Library.

Step Library <a id="step-library"></a>

The catalogue of every step type you can add to a test, organised by category and available in the Step Palette. See Step Library.

Recorder <a id="recorder"></a>

The recording tool, available in the Desktop App, that captures your interactions with an application and converts them into test steps. See Recording a Test.

Tag <a id="tag"></a>

A label used to organise and filter test suites, test cases, and flows. See Tags.

A run configuration that defines how your tests execute, including browser, device, viewport, locale, network, and other settings. See Environments.

A single execution of one or more test cases against one environment. Running against several environments creates one run for each. See Run History.

The unit your plan measures: one test case run against one environment. See Plans & Usage.

A Local run executes on your own computer through the Desktop App. A Cloud run executes on TestOwl's infrastructure. See Triggering a Run.

An automatic run of suites or tests, once or on a repeating pattern. See Scheduling Runs.

Report <a id="report"></a>

The detailed results of a run, including step results, screenshots, video, logs, and an optional PDF export. See Reading Reports.

A reusable value that can be referenced throughout your tests instead of hardcoding data. See Variables.

A secure, write-only value used for sensitive information such as passwords, API keys, and access tokens. See Secrets.

A built-in generator that creates realistic random test data such as names, emails, addresses, dates, and more, through Dynamic variables. See Test Data Generator.

A rule that hides sensitive information in screenshots and videos captured during test execution. See Masking Rules.

Where deleted items are kept for 15 days before being permanently removed, so you can restore them. See Recycle Bin.

An alert in the bell menu, and sometimes an email, about your plan, quota, schedules, or billing. See Notifications.

The permission level assigned to a project member. Available roles are Owner, Admin, Editor, and Viewer. See Project Roles.

The plan a project runs on — Trial, Starter, Pro, or Scale — which determines its limits and features. See Plans & Usage.

The free 7-day evaluation every new project starts with, with all features unlocked and a total of 750 executions. See Plans & Usage.

A project whose trial or access period has ended, or whose payment failed. You can view everything but can't change it or start runs until a plan is active. See Plans & Usage.

The legal name, address, and tax details used on your invoices. See Billing & Subscriptions.