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 for early-stage testing

Staging

Pre-production environment for final validation before release

Production

Live production environment for monitoring real user experiences

Feature Branches

Temporary environments for testing new features in isolation
Each environment can have its own URLs, credentials, and configuration variables, which automatically apply when a test runs in that environment.
Environments dashboard showing multiple configured environments

Environments dashboard showing multiple configured environments

Choose a Default Environment to streamline test configuration and speed up the test run setup process.

​
Key benefits

No Test Duplication

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

Easy Comparison

Compare test results across environments to identify environment-specific issues.

Parallel Testing

Run the same test across multiple environments simultaneously for faster validation.

Environment-Specific Config

Each environment has its own URLs, credentials, and variables that automatically apply.
The Environments page URL tracks your selection: the environment, the tab, and any open property. When you select an environment, switch tabs, or open a property, Spur updates the URL in the address bar. Copy the URL and send it to a teammate. The link opens the same environment, on the same tab, with the same property open.
The recipient needs a Spur login with access to the same Application. If the link points to an environment that was deleted or is not in your selected Application, Spur opens your default environment instead.
Need to temporarily redirect tests to a deploy preview or feature branch URL without changing your environment settings? Use Override URLs to redirect at runtime.