Glossary
Key terms used across QAlity. Jump to a section or scan definitions below.
Test structureTest structure
One saved test flow with steps and checks for a specific user journey. Building block for suites and plans. See Creating test cases and Your first test.
A group of related test cases you run together (by feature, module, or goal). Suites go into test plans. See Creating test suites.
A group of test suites for larger runs. Plans can be scheduled for regular execution. See Creating test plans and Scheduling test plans.
A reusable set of steps saved once and reused across test cases to avoid duplication. See Step Groups.
A reusable UI locator (created by the recorder or edited manually) that cases reference for stable targeting. See Elements.
ExecutionExecution
Visual single-case runner. In Run Configuration it appears as Browser Extension. Live playback in an Incognito window. Test cases only. Suites and plans use Cloud. See Browser Execution and Browser Execution vs Cloud Execution.
Background headless runner shown as Cloud in Run Configuration. Runs cases, suites, and plans. Suites and plans always use Cloud. See Cloud Execution.
Dialog opened from Run / Config & Run where you choose Browser Extension or Cloud and set Advanced Settings (timeouts, environment, Capture Screenshots).
Automatic plan runs at a set date, time, or cadence without a manual click. On Pro and Business, Notification Settings can email the completion report when a scheduled run finishes. See Scheduling test plans.
Machine and browser configuration a plan uses when it executes. Cloud runs use Chromium (Chrome in Advanced Settings).
Results and reportsResults and reports
Run log on a case, suite, or plan showing status, run ID, agent type, message, duration, and step details including screenshots.
Result status meaning the test has never been run. See Understanding test status.
Result status meaning all steps completed and assertions succeeded.
Result status meaning a step error or failed assertion occurred.
Result status meaning the run ended before completion.
Result status meaning someone clicked Stop during an active run.
A future plan run is registered on a schedule, not a finished-run result status.
Live in-progress indicator on an active run detail page, not a final result status.
Images captured during Browser or Cloud runs and attached to steps in Execution History. Timing is controlled by Capture Screenshots. See Viewing screenshots.
Advanced Settings option that controls when images are taken (for example All Steps or Failed Steps).
Downloadable PDF for a completed case, suite, or plan run. It includes summary, step results, and failed step screenshots when captured. See PDF reports.
Workspace home for run volume, success/failure trends, recent results, and next scheduled runs. See Dashboard overview.
REST API testingREST API testing
Feature that turns HTTP calls into reusable tests. Capture live traffic while you browse, generate requests with AI, build them by hand, paste cURL or JSON, or import a definition file. Included free on Discover, Pro, and Business. UI and API cases share one test case limit. API import is Pro and Business only. See REST API Testing.
The list of API requests recorded from a live browser session, each with method, path, and status code. See Record from browser.
HTTP response code shown on every captured or replayed request (for example 200, 201, 204, 401, 500). Assertions use the expected code to decide pass or fail. See REST API Testing.
Expected result on an API request, typically the status code the backend should return. Failed assertions are stored in Execution History.
AuthoringAuthoring
QAlity extension that captures clicks, typing, and navigation as test steps. Installed from the Chrome Web Store via the in-app popup on first Start recording. Works on Chromium-based browsers only (Chrome, Edge, Brave), not Firefox or Safari. See Recorder and Installation.
Continues recording from the end of an existing case after replaying current steps, and covers editing or adding steps. See Re-recording and editing.
Settings flow to export or import project data as JSON (elements, environments, cases, suites, plans) for backup or migration. See Import & Export.
AI featuresAI features
While recording, select an element and choose Generate Steps with AI so QAlity builds steps for that control. See AI Step Generation.
Turns one recorded case into multiple positive, negative, and boundary data scenarios without duplicating entire tests. See Case Variations.
During a run, detects a missing recorded element, finds an updated match, updates the locator, and continues. See Auto-Heal.
Shared billing-cycle quota for all AI features (Auto-Heal, AI Step Generation, Case Variations, API prompts, and other AI-assisted actions), not a separate limit per feature. Discover 50, Pro 500, Business 1000 per cycle. See Pro plan and Business plan.
Data and environmentsData and environments
Named set of reusable parameters (such as base URLs) you attach to a case and reference in steps. See Environments.
Key-value pair in an environment substituted into steps at runtime (for example QA → https://qa.example.com).
Data-driven table that runs the same case once per row with different parameter values. See Data profiles.
OrganizationOrganization
Top-level workspace unit that holds versions and shared case types and priorities. See Projects.
Release or sprint slice inside a project with its own set of test cases. See Versions.
Project-level category for a case’s purpose (for example Functional or Regression). See Case types.
Project-level importance label for a case (for example Low through Critical). See Case priorities.
CollaborationCollaboration
Default role with full workspace control, including Settings, then Users. See User access levels.
Default role for day-to-day testing without user administration. See User access levels.
Admins invite users by email and in-app notification. Accepting an invite to a new workplace removes the user from their previous workplace. If an Admin accepts, all users in that previous workplace are deleted. See Inviting users.
A named set of permissions. Admin and Member are the Default roles. Custom roles are added on the Roles tab and can be assigned to any user. See Roles.
For one project, the View, Create, Edit, and Delete actions a member may use on each module. Role defaults apply unless that member is overridden. See Project permissions.
More guidesMore guides
Continue with these related docs: