CI/CD Integration Overview

CI/CD Integration Overview

LoadGen Functional & Automated Testing integrates seamlessly with popular CI/CD (Continuous Integration/Continuous Deployment) pipelines, enabling automated testing as part of your software delivery workflow.

Supported CI/CD Platforms

LoadGen can be integrated with the following build automation tools:

| Platform | Integration Method |

|----------|-------------------|

| Jenkins | Command-line execution via build steps |

| Azure DevOps | Pipeline tasks with PowerShell/command-line |

| Visual Studio Team Services | Build pipeline integration |

| GitHub Actions | Workflow steps using LoadGen CLI |

| GitLab CI | Job scripts with LoadGen commands |

Command-Line Interface

LoadGen provides command-line parameters that enable automated test execution from any CI/CD pipeline:

`powershell

LoadGenStudio.exe /run /workload:"C:\Tests\MyWorkload.lgw" /output:"C:\Results"

`

Key Parameters

| Parameter | Description |

|-----------|-------------|

| /run | Execute the workload in headless mode |

| /workload | Path to the workload file (.lgw) |

| /output | Directory for test results |

| /timeout | Maximum execution time in seconds |

| /exitcode | Return non-zero exit code on failure |

Integration Benefits

  • Automated Regression Testing : Run functional tests automatically on every code commit
  • Early Bug Detection : Catch issues before they reach production
  • Consistent Test Execution : Eliminate human error from manual testing
  • Detailed Reporting : Generate test reports for each pipeline run
  • Pass/Fail Gates : Block deployments when tests fail

Getting Started

1. Install LoadGen on your CI/CD agent or build server

2. Configure credentials using environment variables or secure secrets

3. Add build steps to execute LoadGen workloads

4. Parse results and integrate with your reporting tools

Example: Jenkins Pipeline

`groovy

pipeline {

agent any

stages {

stage('Functional Tests') {

steps {

bat 'LoadGenStudio.exe /run /workload:"tests/smoke-test.lgw" /exitcode'

}

}

}

post {

always {

archiveArtifacts artifacts: 'results/**', allowEmptyArchive: true

}

}

}

`

Example: Azure DevOps Pipeline

`yaml

steps:

  • task: PowerShell@2

displayName: 'Run LoadGen Functional Tests'

inputs:

targetType: 'inline'

script: |

& "C:\Program Files\LoadGen\LoadGenStudio.exe" /run /workload:"$(Build.SourcesDirectory)\tests\functional.lgw" /exitcode

`

Next Steps

Was this article helpful?
0 out of 0 found this helpful