Action Bindings

Action Bindings connect your defined Actions to specific Environments, allowing the same test to use different configurations based on where it’s running.

Overview

Action Bindings provide:

• Environment Flexibility: Run the same test against different backends
• Configuration Mapping: Map abstract actions to concrete implementations
• Credential Isolation: Use different credentials per environment

Creating Action Bindings

1. Navigate to Integrations → Action Bindings
2. Click New Binding
3. Select the Action to bind
4. Select the Environment to bind to
5. Configure environment-specific overrides:
   • Base URL
   • Authentication headers
   • Request transformations
6. Save the binding

How Bindings Work

When a test runs:

1. The test runner identifies which actions are used
2. Based on the selected environment, it resolves the appropriate binding
3. The binding’s configuration overrides the action’s defaults
4. The request is made with the environment-specific settings

Example

If you have an action called CreateUser:

Each binding ensures the CreateUser action hits the correct endpoint with proper credentials.

Best Practices

• Create bindings for all environments your tests will run in
• Use variables in bindings instead of hardcoding values
• Test bindings in development before production use
• Document custom headers or transformations applied per environment