Overview
Environments let you organize variables into named groups — such as Production, Staging, or Local Dev — so your tests can use different configurations depending on the context they run in. Each environment holds a set of key-value variables that your tests can reference at runtime. Variables can be marked as sensitive to protect secrets like API keys and passwords.
Creating an Environment
Enter details
Provide a Name (e.g., 
Production, Staging) and an optional Description to help your team understand what this environment is for.
Managing Variables
Click any environment row to open its detail drawer, where you can add, edit, search, and delete variables.
Adding Variables
Mark as sensitive (optional)
Toggle Sensitive if the value contains a secret (API key, password, token). Sensitive values are encrypted and masked in the UI.
Editing Variables
Click the pencil icon on any variable row to open inline editing. You can change the name, value, or toggle the sensitive flag (for non-sensitive variables only).Deleting Variables
Click the trash icon on any variable row. A confirmation dialog will appear before the variable is permanently removed.Sensitive Variables
Sensitive variables provide an extra layer of protection for secrets:| Behavior | Detail |
|---|---|
| Masked in UI | Displayed as •••••••• with a lock icon. |
| Hidden from API | The get endpoint returns null for sensitive values. |
| Irreversible | Once marked sensitive, a variable cannot be changed back. |
| Editable value | You can update the value of a sensitive variable, but you won’t see the current value. |
