Environments

Environments allow you to define different configurations for running tests across development, staging, production, and custom environments.

Overview

Environments in Lamdis provide:

• Variable Scoping: Define environment-specific variables that override defaults
• Configuration Isolation: Keep production credentials separate from development
• Easy Switching: Quickly switch between environments when running tests

Managing Environments

Creating an Environment

1. Navigate to Integrations → Environments in the sidebar
2. Click New Environment
3. Provide a name (e.g., “Production”, “Staging”, “Development”)
4. Add environment-specific variable overrides
5. Save the environment

Environment Variables

Each environment can override variables defined at the organization level:

• Base URL: Different endpoints for staging vs production
• API Keys: Environment-specific credentials
• Feature Flags: Enable/disable features per environment

Using Environments

In Test Runs

When running a test suite, select the environment from the dropdown. All tests in the run will use that environment’s configuration.

In CI/CD

Pass the environment ID when triggering tests via API:

curl -X POST https://api.lamdis.ai/v1/runs \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "suiteId": "suite_123",
    "environmentId": "env_456"
  }'

Best Practices

• Never share production credentials in development environments
• Use descriptive names that make it clear which environment is which
• Document environment differences so team members understand what varies
• Test in staging first before promoting changes to production