Test Configuration

Overview

Test configuration is how you keep tests portable across environments. Instead of hardcoding base URLs and tokens into every test, you define them once and inject them at runtime.

What test configuration controls

• Environments (Dev/QA/Staging/UAT/Prod)
• Global variables (base URL, tokens, IDs)
• Common headers (auth, tenant, correlation IDs)
• Datasets for data-driven execution (CSV/JSON/inline)

Typical workflow

1. Create a configuration profile for an environment.
2. Add variables and headers (store secrets in your secret manager).
3. Link the profile to a test case or run.
4. Execute—the platform injects values automatically.

Best practices

• Keep one profile per environment and name them clearly (Dev, Stage, Prod).
• Rotate tokens and secrets; avoid committing sensitive values.
• Use unique IDs per run to prevent collisions.
• Update configuration when endpoints, environments, or auth mechanisms change.

Related articles

• Configuration fundamentals
• Test case
• Test run