Skip to main content

​
What are Environments?

An environment represents a specific deployment of your application where tests can be executed. Common examples include:
  • Development - Your local or dev server
  • Staging - Pre-production environment for final testing
  • Production - Live production environment
  • Feature Branches - Temporary environments for new features
Each environment can have its own URLs, credentials, and configuration variables, which will automatically change when a test is ran in a given environment.

Environments dashboard showing multiple configured environments

Choose a Default Environment to speed up the process of configuring a test run!

​
Key Benefits

No Test Duplication

Write tests once, run them across all environments without copying test code

Environment-Specific Config

Each environment has its own URLs, credentials, and variables

Parallel Testing

Run the same test across multiple environments simultaneously

Easy Comparison

Compare test results across environments to spot inconsistencies

​
What Each Environment Can Have

Environment Variables
Instead of creating “Login Test - Dev”, “Login Test - Staging”, and “Login Test - Production”, create one “Login Test” and run it across all three environments.

​
How Environments Work

1

Configure Environments

Set up your environments (Dev, Staging, Production) with their specific configurations.
2

Create Tests

Write tests that use environment variables instead of hardcoded values.
3

Run Tests

When running a test, select which environment(s) to test.
4

View Results

See separate results for each environment and compare them side-by-side.

​
Next Steps

Configure Variables

Set up environment-specific URLs, credentials, and settings

Run Tests with Environments

Learn how to select environments when running tests

Create Test Plans

Run comprehensive tests across multiple environments