Workspace
A workspace is the top-level in the QA Wolf platform. All environments, groups, and related settings live inside a workspace.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.
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 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.Group
Under each environment are groups, which are collections of flows. Every flow must belong to a group. Each environment can include multiple groups, which makes it easier to navigate, report on, and maintain your flows.Use groups to organize tests by module, feature, or functionality, such as Authentication, Checkout, or Billing.
Flow
Within a group are flows. As a tester, you will need to validate several assertions throughout a user journey (or workflow). Flows are designed so that each assertion can be tested independently. Flows are the primary unit of E2E testing in QA Wolf. They consist of individual tests, support helpers (shared logic or actions), and library dependencies (used to extend framework behavior) that all tests in the flow use. Only flows can be scheduled, tagged, and run individually during a QA cycle.Test
A test is a part of a flow that verifies specific behaviors in your application. Each test focuses on a single feature or action and runs within a flow.Run
A run 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 a run 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.Use schedules to execute flows at specific times (12:00a midnight) or at recurring intervals (every hour), or when a build is deployed.