Microsoft ADO Test Plan Integration



In Azure DevOps, manually running test cases for every release can quickly become repetitive and time-consuming. You might manage tests using test plans or create individual work items and execute them manually.

With this integration, you can automate those test cases in Leapwork, run them as often as needed, and easily analyze execution reports and results directly in ADO.


Note: The screenshot on this page uses the Elegance Design, introduced in 2025.3. If you are using an earlier version, your layout may look different.

Import ADO test cases in Leapwork

Once ADO connection is created, we can import flows as part of test cases in Leapwork. 

  1. Right click in the left window.

  2. Select Import from ADO.

image-20260316-123825.png
  1. In the import window, select the ADO project you want to import test cases from.

  2. Select an Area Path to filter the test cases within the selected project.

  3. Click Import.
    Note: Only test cases marked as Planned in ADO, under the Automation Status field, will be imported.

image-20260115-093344.png

The test cases are imported successfully.

  1. Click OK.

image-20260313-151303.png
  1. On left, the test cases are created in project folder Leapwork-ado-sbx. Within the project folder, the structure is defined by the area in ADO.

image-20260115-093515.png
  1. Click to expand a project folder. The ADO imported test cases list appears. The test case filename includes testcase id and test case name.

After importing all test cases, you can start recording flows and executing test cases using a run list. The linked test case and its summary are automatically displayed in the Flow settings.

Sync ADO test cases in Leapwork flow

Important: The option to sync ADO test cases is available starting from release 2024.1.486. If you are using an earlier release, this feature will not be available. Please ensure your Leapwork version is up to date to access this functionality.

When your project is ready to sync, you’ll see a banner at the top of the flows list.

  1. Click Review button.

image-20260316-123908.png
  1. Select a project. All projects associated with the ADO sync appear.

image-20260115-093718.png
  1. Click Sync.
    Note: Only test cases marked as Planned or Automated in ADO, under the Automation Status field, will be synced.

  2. Once the sync finishes, a confirmation pop-up window appears. Click Ok

image-20260115-093845.png

Important notes when syncing

What happens during synchronization with Azure DevOps


  • Deleted test cases in Azure DevOps: If a test case or project is accidentally deleted in Azure DevOps and you click Sync in Leapwork, the corresponding test cases are not deleted in Leapwork. This helps protect your existing automation flows.

  • Test case status changes:

    • If a test case is permanently deleted or marked as Not Automated in Azure DevOps, the related flow in Leapwork is updated to Retire during synchronization.

    • If the test case is later moved back to Planned, the flow in Leapwork is updated from Retire to Draft during the next sync.

  • New test cases added in Azure DevOps: Test cases added after the initial import are not automatically pulled in during synchronization. The Sync function only updates existing flows and test cases.

To bring in new test cases, use the Re-import option in Leapwork.

Import ADO test plan in Leapwork

  1. In Run lists, right click.

  2. Select Import from ADO.

image-20260316-123941.png
  1. Select a project. All the test plans related to that project appears. Each test plan is created based on the test suite and configuration.  

  2. Select a test plan and click Import.
    Note: Only test points marked as Planned or Automated in ADO, under the Automation Status field, will be imported.

image-20260313-151350.png


  1. Click View Details. If there is no test case in a test plan, a message appears - Automated test cases are not available in ADO.
    The information displayed in the ADO Import pop-up window is dynamic based on the result of the importing process:

    • TC Successfully Imported: Imported all suitable test points successfully.

    • Automated TC Not Available: It displays the test cases not imported due to unavailability in ADO or Leapwork.

    • Collision: It displays scenarios where Leapwork already has manually created run lists or folders with the same names in the run list section.

image-20260115-094057.png
  1. Click OK. On the left, run list and configurations appears. Each run list has test cases that you imported in previous steps. Runlist is created on the basis of configuration (Windows 10/11).

  2. Right click on a run list and select New schedule.

image-20260316-124015.png
  1. Enter title of the schedule and click Save. The new schedule is created on the left.

image-20260316-124042.png
  1. Right click on the new schedule.

  2. Select Run Now.

image-20260316-124119.png

Publish execution results on ADO

In ADO, you can verify that while execution, test run is in progress or completed as shown below.

image-20260115-094253.png
  1. In ADO, click refresh.

  2. Click on a test run.

  3. Click Run summary. On right in pie chart, you can see that the result shows that one test case passed and one failed.

image-20260115-094316.png
  1. Click Test Results. You can see that the result shows that one test case passed and one failed.
    Note: Once a test case is run, the status of that test case will be automatically change from Planned to Automate in ADO, under the Automation Status field.

image-20260115-094350.png
  1. Click Progress Report. You can analyze results based on test suits and available filters.

image-20260115-094421.png

Create bugs from Leapwork to ADO

You can create bugs directly in Leapwork, these bugs will then be reflected in ADO.

  1. In Leapwork, click Reporting.

  2. Right click on a specific flow with Failure Status.

  1. Select Create a bug in ADO.

image-20260115-094516.png
  1. On the Create a bug in ADO pop-up window:

Perform the following steps:
  1. Enter the title of the bug in the Title field.

  2. Click on the Priority drop-down and select a priority from 1 to 4.

    Note: The default option from ADO is 2.

  3. Click on the Severity drop-down and select a severity from 1 (Critical) to 4 (Low). 

    Note: The default option from ADO is 3.

  4. Enter the build number or version of the bug in the Found in build field.

  5. Fill in any additional custom fields configured in the Azure DevOps Connections section.

  6. Give the reproduction steps in the Repro Steps field. 

  1. Click Create.

image-20260115-094539.png

The bug has been created successfully in Leapwork and is now reflected in Azure DevOps.