Environments

Run tests against staging, preview, and other environments

Environments let you run tests and suites against different base URLs — like staging or preview deployments — without modifying your test configurations.

Creating an Environment

1. Go to the Tests page and navigate to Environments
2. Click New Environment
3. Fill in the details:
   • Name — A label for this environment (e.g., “Staging”, “Preview”)
   • URL — The base URL (e.g., https://staging.example.com)
   • Tokens (optional) — Key-value pairs for API keys or auth tokens needed in this environment
4. Click Create

Running Tests Against an Environment

Once you’ve created environments, a dropdown appears on the Run button for both individual tests and suites:

• Individual tests — Click the Run Test dropdown and select an environment. The test runs against that environment’s URL instead of the original.
• Suites — Click the play button on a suite row and choose an environment, or select Default (original URLs) to run with the original test URLs.

Create separate environments for each deployment target your team uses (staging, QA, preview branches). Any test or suite can be run against any environment on demand — no configuration changes needed.

Managing Environments

From the Environments page, you can:

• Edit — Click the pencil icon to update the name, URL, or tokens
• Delete — Click the trash icon to remove an environment

Tokens

Tokens are key-value pairs passed to your tests as environment-specific configuration. Common uses include:

• API keys that differ between environments
• Auth tokens for service-to-service authentication
• Feature flags or configuration overrides

Add tokens when creating or editing an environment by clicking Add Token and entering a key and value.