Run Configuration

Overview

Run Configuration allows you to customize how workflows execute. Configure execution parameters, environment settings, retry behavior, and other runtime options to optimize your test execution.

---

Configuration Options

Basic Configuration

Run Configuration
├── Environment: Dev / Staging / Production
├── Execution Mode: Sequential
├── Timeout Settings: Global & per-step
├── Retry Policy: Automatic retries on failure
├── Data Set: Select test data profile
├── Browser/Platform: Target browser or device
└── Custom Parameters: Variables for workflow

---

Environment Selection

Setting Execution Environment

1. Open workflow

2. Click "Run Configuration" or "Settings"

3. Select "Environment" dropdown

4. Choose target environment:

   • Development

   • Staging

   • UAT

   • Production

5. Save configuration

Environment-Specific URLs

Different URLs for each environment:

Development:   https://dev.example.com
Staging:       https://staging.example.com
UAT:           https://uat.example.com
Production:    https://example.com

Override at Runtime

You can override environment when manually running a workflow:

1. Click "Run"

2. Choose "Run With Configuration"

3. Select different environment

4. Execute with custom environment

---

Execution Modes

Sequential Execution

Steps run one after another:

Start
  ├── Step 1: Runs (blocks until complete)
  ├── Step 2: Starts after Step 1 completes
  ├── Step 3: Starts after Step 2 completes
  └── End: After all steps complete

Use When:

• Steps depend on previous results

• Data propagation between steps required

• Session must be maintained

• Order is critical

Execution Configuration

Execution Strategy

Start
  ├── Phase 1 (Sequential):
  │   ├── Step 1: Login
  │   ├── Step 2: Navigate
  │   └── Step 3: Prepare data
  │
  ├── Phase 2 (Optimized):
  │   ├── Step 4A: Test feature A
  │   ├── Step 4B: Test feature B
  │   └── Step 4C: Test feature C
  │
  └── Phase 3 (Sequential):
      ├── Step 5: Logout
      └── Step 6: Verify cleanup

---

Timeout Configuration

Global Timeout

Default timeout for entire workflow:

Global Timeout: 30 minutes
├── If any step exceeds 30 minutes
└── Entire workflow is terminated

Per-Step Timeout

Individual timeout for each step:

Step Configuration
├── Step 1: Timeout = 5 minutes
├── Step 2: Timeout = 2 minutes
├── Step 3: Timeout = 10 minutes
└── Global: 30 minutes (max)

Setting Timeouts

1. Open run configuration

2. Click "Timeout Settings"

3. Set global timeout (or use default)

4. Per step:

   • Click step

   • Set individual timeout

5. Save

Timeout Behavior

Step Execution
├── Timeout expires
├── Step terminates
├── Next step:
│   ├── Continue (if not dependent)
│   └── Skip/Fail (if dependent)
└── Workflow status: Partial/Failed

---

Retry Configuration

Automatic Retry Settings

Configure how failures are handled:

Retry Configuration
├── Max Retries: 0-10 attempts
├── Retry Delay: 1-300 seconds
├── Backoff Strategy: Linear / Exponential / Fixed
├── Retry Condition: On any error / specific errors
└── Fail After: Stop retrying after X attempts

Retry Strategies

No Retry

Failure → Workflow fails immediately

Fixed Retry

Attempt 1: Fails
Wait 5 seconds
Attempt 2: Fails
Wait 5 seconds
Attempt 3: Succeeds or Max attempts reached

Exponential Backoff

Attempt 1: Fails (immediate)
Wait 2 seconds
Attempt 2: Fails
Wait 4 seconds
Attempt 3: Fails
Wait 8 seconds
Attempt 4: Succeeds

Configure Retries

1. Open run configuration

2. Click "Retry Policy"

3. Enable retries

4. Set max attempts (recommended: 3-5)

5. Choose backoff strategy

6. Set delay between retries

7. Save configuration

---

Test Data Selection

Data Sets

Pre-defined test data profiles:

Data Sets Available:
├── Standard Users
│   ├── [email protected]
│   ├── [email protected]
│   └── [email protected]
├── Edge Cases
│   ├── empty_user
│   ├── special_chars_user
│   └── max_length_user
├── International
│   ├── chinese_user
│   ├── arabic_user
│   └── emoji_user
└── Custom (user-defined)

Select Data Set at Runtime

1. Open workflow

2. Click "Run"

3. Select data set from dropdown

4. Execute with chosen data

Benefits

• Run same workflow with different data

• Test with edge cases

• International character testing

• Multiple user scenarios

---

Browser and Platform Configuration

Web Testing

Browser Selection
├── Chrome (latest, specific version)
├── Firefox (latest, specific version)
├── Safari (latest, specific version)
├── Edge (latest, specific version)
└── Multiple browsers (run on each)

Mobile Testing

Platform Selection
├── iOS (device model, version)
├── Android (device model, version)
└── Both (run on both)

Desktop Testing

Platform Selection
├── Windows 10 / 11
├── macOS (version)
├── Linux (distribution)
└── Custom resolution

Setting Platform

1. Open run configuration

2. Click "Browser/Platform"

3. Select browser or device

4. Choose version (optional)

5. Set options:

   • Screen resolution

   • Device orientation (mobile)

   • Browser window size

6. Save

---

Custom Parameters

Define Workflow Variables

Create variables for flexible workflows:

Custom Parameters
├── username: ${test_user}
├── password: ${test_password}
├── environment_url: ${env_url}
├── test_data_id: ${data_id}
└── custom_flag: ${feature_flag}

Using Parameters in Workflow

Reference in steps:

Step 1: Login
├── Username: ${username}
├── Password: ${password}
└── Base URL: ${environment_url}

Step 2: Navigate
├── URL: ${environment_url}/dashboard

Override at Runtime

Default Configuration:
├── username: [email protected]
├── environment_url: https://staging.example.com

Runtime Override:
├── username: [email protected]
├── environment_url: https://prod.example.com

---

Advanced Configuration

Execution Policies

Control how workflow behaves on failures:

Fail Fast: Stop on first failure Continue on Error: Skip failed steps, continue workflow Retry on Error: Retry before moving next Conditional: Use custom logic

Timeout Limits

Prevent resource overload:

Maximum Execution Timeout: 24 hours
├── Limits how many steps run simultaneously
├── Prevents system overload
└── Balances resource usage

Resource Allocation

Resource Configuration
├── Memory: Allocate per workflow
├── CPU: Core allocation
├── Network: Bandwidth limits
└── Storage: Temporary file storage

---

Real-World Examples

Example 1: Multi-Environment Testing

Configuration Template: E-Commerce Checkout

Staging Run:
├── Environment: Staging
├── Browser: Chrome (latest)
├── Data Set: Standard Users
├── Retries: 3
├── Timeout: 15 minutes
└── Purpose: Pre-production validation

Production Smoke Test:
├── Environment: Production
├── Browser: Chrome (latest)
├── Data Set: Critical Path (minimal)
├── Retries: 5 (more aggressive)
├── Timeout: 10 minutes
└── Purpose: Quick production check

Example 2: Cross-Browser Testing

Configuration: Web Application

Chrome:
├── Environment: Staging
├── Browser: Chrome 120
├── Platform: Windows 11
├── Resolution: 1920x1080
└── Run all tests

Firefox:
├── Environment: Staging
├── Browser: Firefox 121
├── Platform: Windows 11
├── Resolution: 1920x1080
└── Run all tests

Safari:
├── Environment: Staging
├── Browser: Safari 17
├── Platform: macOS 13
├── Resolution: 1440x900
└── Run subset of tests

Example 3: Load Testing Configuration

Configuration: Performance Test

Execution Settings:
├── Max Execution Steps: 10
├── 10 simulated users
├── 20 checkout workflows
├── Run sequentially

Timeout:
├── Global: 60 minutes
├── Per-step: 30 minutes

Retry:
├── Disabled (need accurate timing)

Purpose: Measure system under load

---

Configuration Templates

Save Configuration as Template

1. Configure workflow as desired

2. Click "Save as Template"

3. Give template name: "Production Safe Run"

4. Save

Apply Template

1. Open workflow

2. Click "Load Template"

3. Select template: "Production Safe Run"

4. Configuration loads

5. Execute with template settings

Built-in Templates

Available Templates:
├── Quick Smoke Test
│   ├── Minimal timeouts
│   ├── Max retries
│   └── Fast execution
├── Thorough Testing
│   ├── Long timeouts
│   ├── Detailed execution
│   └── Comprehensive checks
├── Production Safe
│   ├── Conservative retries
│   ├── Extended timeouts
│   └── Fail-safe settings
└── Performance Testing
    ├── Sequential execution
    │   └─ Steps run one after another
    ├── Resource limits
    └── Load simulation

---

Monitoring Configuration Impact

Performance Metrics

Track configuration effectiveness:

Execution Time: 8m 32s (with config)
├── Sequential only: 14m 20s
├── Optimized sequence: 8m 32s
└── Improvement: 40% improvement

Success Rate: 97%
├── Without retry: 89%
├── With retry (3 attempts): 97%
└── Improvement: 8% more reliable

Resource Usage

Monitor resource consumption:

Memory: 512 MB (with limits)
CPU: 40% utilization
Network: 5 Mbps average
Storage: 256 MB temporary files

---

Best Practices

✅ Do

• Create templates for common scenarios

• Test configuration before scheduling

• Document configuration choices

• Monitor impact on performance

• Use environment separation

• Set reasonable timeouts

• Implement retry strategies

• Regular configuration review

❌ Don't

• Use production settings casually

• Set excessive timeout values

• Retry permanent errors

• Run workflows without limits

• Forget to test configuration changes

• Mix unrelated parameters

• Leave default configurations

• Ignore resource constraints

---

Troubleshooting

Issue: Workflow takes too long

Solutions:

1. Configure execution for your workflow

2. Reduce timeout values

3. Optimize step execution

4. Use faster browser

5. Check network connectivity

Issue: Workflow fails randomly

Solutions:

1. Enable retry with backoff

2. Increase timeout values

3. Review step dependencies

4. Check error logs

5. Verify environment stability

Issue: Resource exhaustion

Solutions:

1. Adjust execution timeout limits

2. Increase delay between steps

3. Use more powerful machine

4. Split workflow into smaller ones

5. Monitor resource usage

---

Related Topics

• Scheduler

• Execution Flow

• Error Handling

• Performance Optimization

• Reports