Environments

Environments

An environment is a named target system where tests are executed — Development, Staging, Production, or any custom system you define. Environments exist so the same test suite can run against different systems without duplicating the suite itself: one set of test cases, many possible targets.

Why Environments Are Separate from Launches

A launch is a single test run; an environment is a reusable configuration that a launch points at. Separating the two means:

• The same suite can be run against Staging today and Production tomorrow without being rewritten.
• Configuration that's specific to a target system — its base URL, credentials, custom headers — lives in one place instead of being copy-pasted into every test.
• Historical results retain which environment they ran against, even if that environment's configuration later changes.

What an Environment Holds

Each environment has a base URL, an optional set of variables (plain values, secrets, or file references), custom headers sent with every request, and an authentication configuration (API key, bearer token, basic auth, or OAuth 2.0). Variables support a three-level override hierarchy — launch-level values override environment-level values, which override global workspace-level values — so a team can set sensible defaults once and only override what's actually different per environment.

One environment in a project is marked as default, pre-selected whenever a new launch is created.

Related

• Environments Reference — full UI reference for creating, editing, and managing environments and their variables
• Executing Tests — selecting an environment when running tests
• Projects — environments are configured per project