Environments

Environments define where test runs execute.

Create an environment

1. Go to Environments -> Create.
2. Fill Name and Base URL.
3. Optionally fill API Base URL, Username, and Password.
4. Save.

Validation rules

• Name: required.
• Base URL: required and must be a valid URL.
• API Base URL: optional; if provided, must be a valid URL.

Usage in test runs

• Each test run requires one selected environment.
• Environment-aware navigation and wait steps read this configuration at runtime.
• Environment data drives base URL resolution and target context for the run.

Usage in locator capture

• The locator creator can launch its Chromium picker from a saved environment.
• This is useful when you want to inspect a known application target without retyping the URL.
• For one-off pages, the locator creator also supports launching directly from a URL without saving an environment first.

Tips

• Use stable names like Local, Staging, Prod-Snapshot.
• Keep secrets local; avoid committing sensitive .env values.