An important part of automated test monitoring and control is to monitor, inspect, and react to the results. This is best accomplished in the test management and bug tracking system that we use for our daily work.
In this article, we can review three different scenarios on how to trigger and create/update bugs in the Azure DevOps Server, formally known as Visual Studio Team Services (VSTS) or Team Foundation Server (TFS), based on the results of test cases running in Leapwork.
Use a plugin for Azure DevOps Servers
Use the Leapwork plugin to easily integrate with the Azure DevOps Servers. This extension can be installed from the Visual Studio Marketplace as follows:
Navigate to the Visual Studio Marketplace.
Type Leapwork in the search bar and select it.
Now go back to the Project in DevOps and Select the required project in DevOps.
Now create a release pipeline for the associated project. Select the project and in the sidebar, select the Pipelines option and select Releases.
To add a new pipeline, select New and choose the "New release pipeline" option.
Select a required job for this step or just start with an "Empty job"
After adding the job, click on the Save button.
Now to add a task, select the Task option.
To add a task to an agent job, click on the "+" (highlighted below.)
Type Leapwork in the search bar and press enter.
Click on Add.
Now the task will be shown on the left panel and choose that task by selecting the checkbox.
- Enter Leapwork controller hostname or IP-address.
- Enter the Leapwork controller API port, by default it is 9001.
- Enter the API access key. We can find it in Leapwork Controller Settings section.
- Enter time delay (in seconds, by default 5 seconds). While a schedule is running extension will check the schedule state with a specified delay before the schedule is finished.
- Select how the extension should process "Done" status: “Success” or “Failed”.
- Enter the JUnit report file name. The default name is "report.xml".
- Enter schedule titles we want to run, each one must be entered from a new line.
- Enter schedule ids, each one must be entered from a new line. Using id is preferable because the schedule title can be changed.
After entering all the required inputs, click on the Save button.
Now navigate back to the pipeline and click on the "Create a Release" option.
Click on a Stage(Stage 1) and click on create to create a release.
Now to deploy the release, click on either Release or Stages.
Click on Deploy.
Now the release will be queued.
For any clarification, please contact our Priority Support.