Environments

Define named environments (staging, production, preview) with distinct base URLs, credentials, and configuration. Run the same test plan against multiple environments.

What is an environment?

An environment is a named configuration profile that specifies:

• The base URL to run tests against
• Credentials (test user accounts, API keys, bearer tokens)
• Any environment-specific variables (feature flags, custom headers)

Test plans reference an environment by name. The same plan can be run against staging for pre-deploy checks and against production for post-deploy smoke tests.

Creating an environment

Navigate to Project Settings → Environments → Add Environment:

Field	Description
Name	Short identifier: staging, production, preview
Base URL	Full URL including protocol: https://staging.myapp.com
Default environment	If checked, this environment is used when no environment is specified in a run trigger

Credentials

Add credentials per environment under Environments → [name] → Credentials:

• Test user account — email/password for logging in via Web UI tests
• API bearer token — pre-issued token for API tests (or a login endpoint + credentials to obtain one at test setup)
• API key — header name and key value
• Admin account — separate credentials for scenarios that require elevated privileges

All credentials are encrypted at rest and are only decrypted in the test execution environment. They are never exposed in logs or UI.

Environment variables

Add arbitrary key-value pairs per environment that are injected into the test execution context. Useful for:

• Feature flag values that differ between environments
• Custom request headers (e.g. bypassing rate limits in staging)
• Test data identifiers (e.g. a known product ID that exists in staging)

Specifying environment in a run trigger

POST https://api.sentinelflux.in/v1/runs
{
  "project": "myapp",
  "plan": "smoke",
  "environment": "staging"
}

If environment is omitted, the default environment for the project is used.