Project ID: Enter the project ID. If you don't specify project ID, test will get created in the default project.
Show Log: When this flag is checked, log file will be displayed in the console.
Total Users: Select the number of users you want to deploy at the peak of your test.
Duration (min): You can configure your test to run for a specified duration.
Ramp up Time (min): Select how fast you want the test to ramp-up. This is the elapsed time in minutes from test start until all users are running.
Ignore SLA: When this flag is checked, regardless of the SLA, build will succeed.
Update Main Test File: Select this to upload main test file for existing test.
Report Name: Enter report name.
Create Multitest: Select this to create a new multitest.
Run Existing Performace Test: Select this to run existing performace test.
Multitest File: Upload json file for create multitest.
Upload Json File:Upload json file for existing performance test and create performance test
webhook: Send test result notification to slack or teams.
Release notes
New in 2.9.2
Added Resiliency to ADO plugin when it fetches the Report data from BlazeMeter during the test execution
New in 2.9.1
Handled test status change due to Data Processing delays
New in 2.9.0
Added slack and teams webhook
New in 2.8.0
Fixed JMX File issue
New in 2.7.0
Added private location
New in 2.6.0
Added stop test feature (BlazeMeter Integration Stop Test Functionality Plugin)
New in 2.5.0
Bug fixes
New in 2.4.0
Added to run existing multitest and create new multitest in blazemeter functionality
Added upload json for existing pereformance test and create new performance test
New in 2.3.0
Bug fixes
New in 2.2.0
Added Report name
New in 2.1.0
Added No Data = failed and Not Set = success for test result
New in 2.0.0
Master ID available in pipeline variable and which can be used in subsequent task
Upload/Replace the main test file for a existing test
Added Ignore SLA - Here if the checkbox is enabled, regardless of the SLA, build will succeed
New in 1.9.9
Public Report URL available in pipeline variable and can be used in sub-sequent task
New in 1.9.8
Bug fixes
New in 1.9.7
Public report URL generation based on test type
Bug fixes
New in 1.9.6
Public report URL is added
New in 1.9.5
Allow user to create Taurus test
Allow functional suite execution
New in 1.9.4
Update allow multi test execution
New in 1.9.2
Bug Fixes
New in 1.9.1
Fix for task execution warning
New in 1.8.0
Upgrade the task execution sdk
New in 1.7.0
Create Blazemeter Performance Test functionality
Update test functionality
Support for test script upload
New in 1.4.0
Allow user to use variables within Test URL
New in 1.3.0
Support for GUI Functional Tests
New in 1.0.0
Execute BlazeMeter tests in azure pipelines
Works with single tests
Fails the task in case of SLA failure
Ability to display logs on screen
BlazeMeter Integration Stop Test Functionality
Usage
Add a new task, select BlazeMeter Integration Stop Test Functionality from the Test category and configure it as needed.
Parameters include:
Graceful Shutdown: Sends a signal to close the test, archive test and log files, then generate an artifacts.zip archive.
Terminate Test: Terminates all servers immediately. This will result in the loss of all test and log files (except for the ones you originally uploaded). No artifacts.zip archive will be generated. This should be a last resort, since without any log files, it will be impossible to identify what may have caused a problem.
Note
Add the custom condition in plugin i.e 'eq(variables['Agent.JobStatus'],Canceled')' to run the task.
