Releases: Azure/load-testing
Releases · Azure/load-testing
Adding a parameter to ignore the wait for the test run completion
Using this tag and version, now you can just trigger the test-run from the work-flow without blocking the same until the test-run completion.
Use waitForTestRunCompletion: false from the task and we don't wait for the test-run completion, we only upload artifacts and start the test, and exit the task gracefully with suucceded state not affecting your workflows.
Fix minor issues for headers
v1.2.2 Fixing the header sanitisation to allow only Ascii characters. (#136)
GitHub Action for Azure Load Testing
Automate your GitHub Actions workflow to load test using Azure Load Testing
Sample workflow to run a load test using Azure Load testing
# File: .github/workflows/workflow.yml
on: push
jobs:
# This workflow contains a single job called "loadtest"
loadtest:
name: Load Test
runs-on: ubuntu-latest
steps:
- name: Checkout GitHub Actions
uses: actions/checkout@v2
- name: Login to Azure
uses: azure/login@v1
continue-on-error: false
with:
creds: ${{ secrets.AZURE_CREDENTIALS }}
- name: 'Azure Load Testing'
uses: azure/load-testing@v1
with:
loadTestConfigFile: 'SampleApp.yaml'
loadTestResource: 'loadTestResourceName'
resourceGroup: 'loadTestResourceGroup'
Fixed issue with missing node modules
v1.2.1 fix for main. (#133)
Auto stop on exceeding VUs per engine
v1.1.28 [AutoStop Max VU] Update API version to 2025-03-01-preview and add mi…
Minor fixes
v1.1.27 few fixes found from UTs etc and headers fixes. (#122)
v1.1.26
Support App Components, server side failure criteria
Added support for Locust tests
[Multi-Engine] Cleanup Locust flag (#103) (#104) * Remove locust flag * Add Locust E2E sample file
Fixed minor issues
v1.1.24 changes for EINVAL issue reported by customer, latest version changes…