> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qawolf.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Glossary

> Definitions of key QA Wolf terms including workspaces, environments, groups, flows, runs, and maps.

## Workspace

A **workspace** is the top-level container in the QA Wolf platform. All environments, groups, and related settings live inside a workspace.

<Note>
  Use workspaces for separate applications, such as the web, iOS, and Android versions of your product. Or when different business units are responsible for completely separate test suites.
</Note>

## Environment

Under each workspace is an **environment**, which corresponds to a specific version of your app, such as development, staging, or production.

Each environment can be [configured](/qawolf/Environment-settings-2cd5b2a994fb8014ba8bd7aa25f3ed0f) with separate variables (e.g., base URL, users, etc.), concurrency rates, and other settings relevant to the version of the application you're testing. Flows and tests are unique for each environment and not shared between environments.

## Map

The **map** shows the flows in an environment and how they are organized into folders. It provides a structured view of your tests so you can navigate and manage flows and tests more easily.

## Flow

A **flow** is a sequence of tests that validates a user journey in your application.

Flows are the primary unit of end-to-end testing in QA Wolf. Flows can be run individually, scheduled, and tagged.

## Test

A **test** verifies a specific behavior or step in your application. Multiple tests combine to form a flow that validates a complete user journey.

<Tip>
  **Example: QA Wolf application hierarchy**

  | Item        | Example                 |
  | :---------- | :---------------------- |
  | Workspace   | Wolf Corp               |
  | Environment | Staging                 |
  | Folder      | accounts                |
  | Flow        | happy-path-ios.flow\.js |
</Tip>

## Run

A [run](/qawolf/Run-a-flow-or-suite-2a25b2a994fb8014b164d7ad2efd5ddel) is an execution of one or more flows. Each flow is attempted up to three times per run if it fails. Runs can be started manually or invoked automatically by a schedule. The status and results of every flow in a run are recorded and reported back.

## Attempt

Within a run, a flow may be attempted multiple times. As a tester, you will occasionally have flows that flake — attempting to run a failed flow multiple times ensures that the failure is not a temporary fluke.

QA Wolf will attempt to run a flow up to three times. Each attempt has its own video, logs, and results, allowing you to isolate issues precisely.

## Schedule

A schedule defines when and how often runs occur automatically. Scheduling is limited to flows. Individual tests can be run manually for debugging, but they cannot be scheduled independently.

<Note>
  Use schedules to execute flows at specific times (midnight) or at recurring intervals (every hour), or when a build is deployed.
</Note>