Displaying Tags from JUnit XML in Azure DevOps Test Results

Question

Displaying Tags from JUnit XML in Azure DevOps Test Results

Martin Bečka 25

Hello,I am using the PublishTestResults@2 task during testing in Azure DevOps with a JUnit .xml file. I would like to make Tags visible in the Test Results web tab.

I have tried adding a <property name="Tags" value="..."/> element under <testcase><properties>, but the tags are not appearing in the UI.

Is there any supported way to make Tags from a JUnit XML visible in the web test results tab?

Thank you.

Best regards, Martin

obrazek

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Anurag Rohikar 3,190 Microsoft External Staff Moderator

Hello Martin, Thanks for reaching out on Microsoft Q&A!

Currently, the PublishTestResults@2 task in Azure DevOps only parses a limited subset of the JUnit XML schema. While elements such as test case name, class name, duration, error/failure messages, and stack traces are supported, custom metadata like <properties> or <property name="Tags" … /> are not displayed in the Test Results web tab.

That’s why the tags you’ve added under <testcase><properties> are not appearing in the UI. Since this feature isn't supported out-of-the-box, the most effective approach is to use a workaround.

Workarounds

Embed tags in test names
Include tags directly in the test case name so they show up in the results grid:
```
   <testcase classname="LoginTests" name="[Smoke][UI] should login with valid user" time="0.12"/>
```
Documentation: Publish Test Results task
Use TRX format (if applicable)
If your framework supports TRX (for example with MSTest or VSTest), you’ll get richer integration with Azure DevOps Test Explorer, and you can map categories more easily.
Azure Test Plans
If you need filterable/searchable tags in the Azure DevOps portal, the supported approach is to manage your test cases within Azure Test Plans, where tags and custom fields are first-class citizens.
Documentation: Manage Test Cases
Custom reporting
For advanced test reporting needs, consider integrating with tools like Allure or ReportPortal and publishing a link in your pipeline summary. This way you can expose tags and other metadata outside of the default Azure DevOps test tab.
Documentation: Integrating Allure with Azure Pipelines
Disclaimer: This document is not maintained by Microsoft. It is being shared solely for your convenience.

At this time there’s no supported way to surface JUnit <properties>/tags in the Azure DevOps Test Results web tab. The recommended workaround is embedding them in test names or using Test Plans for richer test management.

Hope the above helps! Let us know if you have any further question. Thank you!

Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator

2025-09-03T08:35:33.0766667+00:00

Hello Martin Bečka, just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this. Thank you!
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Martin Bečka 25 Reputation points

2025-09-03T10:29:57.2233333+00:00

Hello,

Thank you for your answer.

I am not sure why my previous comment was removed, so here is a brief version:

Could we elaborate a bit further on the use of Azure Test Plans? Currently, my team maintains a regression test plan for each iteration, with more than 1,000 test cases. Up to now, we have been marking the test points manually after the automated tests were executed. Our original intent was to use tags in the Test Results tab to provide quick feedback to development teams before proceeding with test point updates.

If we were to instead use tags within Test Plans, is there a way to automatically map the output of a JUnit test case to a specific Test Point in our latest test plan?

Thank you once again for your guidance.

Best regards, Martin
Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator

2025-09-03T12:02:50.6433333+00:00
Hello Martin, Thank you for your follow-up! I understand your scenario better now you have a large regression suite, and your goal is to surface test metadata (like tags) quickly for development teams without manually updating thousands of test points.

Key points about Azure Test Plans and automation

Mapping JUnit test cases to Test Points Azure Test Plans is designed to manage manual and automated test points, but there isn’t a built-in way to directly map a JUnit <testcase> from a pipeline run to a specific Test Point just by test name or tag. The mapping of automated tests to Test Points usually relies on:

Test Case IDs linked in the code (e.g., MSTest [TestCaseId(1234)] or NUnit [TestCaseId])

Or custom scripts that match test names to Test Case titles in the Test Plan.

So, for JUnit tests, you would typically need a mapping layer in your pipeline that associates the test case name (or class + method) to the corresponding Test Case ID in Azure Test Plans.

Automated Test Result Publishing

If you convert your JUnit results to TRX format, you can use the VSTest@2 task in Azure Pipelines to publish results and automatically associate them with Test Cases in Test Plans.

Alternatively, the Azure DevOps REST API allows programmatic updating of Test Points and Test Runs. You could implement a script that:

Reads the JUnit XML.

Maps each <testcase> to the corresponding Test Case ID in your Test Plan.

Updates the Test Run with the outcome (Pass/Fail).

This is effectively what many teams do when integrating non-.NET frameworks with Azure Test Plans.

Using tags in Test Plans Tags applied in Azure Test Plans are useful for filtering Test Points and generating queries, but they cannot be automatically populated from JUnit XML. You would need a custom step in your pipeline to translate your JUnit tags into either:

Test Case tags, or

Custom fields on the Test Run/Test Point via the REST API.

Recommended approach for your scenario (in-short):

Maintain a mapping table (e.g., JSON, CSV, or YAML) from JUnit test names to Test Case IDs.

Use a pipeline script (or Azure DevOps REST API) to publish the test results and update Test Points programmatically.

Optionally, convert JUnit results to TRX if your team is open to that, which simplifies Test Plan integration.

References:

Azure Test Plans - Automated Test Integration

Azure DevOps REST API - Test Points

Publish Test Results Task

Hope this helps clarify the options and next steps for automating your regression feedback process! If it helps, please upvote and accept the answer. Thank you!
Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator

2025-09-04T15:49:26.14+00:00

Hello Martin, Just checking to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this. Thank you!
Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator

2025-09-05T08:13:54.27+00:00

Hello Martin Bečka, following up to see if you have a chance to check my previous response and helped, do let me know if you have any further questions on this. Thank you!
Martin Bečka 25 Reputation points

2025-09-05T14:40:53.51+00:00
Hello,

After considering the current situation, I think the best option for us is to use a reusable Python script (which we can apply across multiple projects). The idea is to publish automated test results via the Azure DevOps REST API after the tests are completed.

Are there any official resources or examples that could help with such an implementation? Specifically, I am not sure about the following points:

Maps each <testcase> to the corresponding Test Case ID in your Test Plan.

Updates the Test Run with the outcome (Pass/Fail).

Thank you very much.

Best regards, Martin
Anurag Rohikar 3,190 Reputation points Microsoft External Staff Moderator

2025-09-08T17:45:32.9866667+00:00
Hello Martin,

That’s a solid approach using a reusable Python script with the Azure DevOps REST API gives you full control and can scale across projects.

Official resources you can start with

REST API for Test Runs / Test Results

Test Runs – Azure DevOps REST API

Test Results – Azure DevOps REST API These endpoints let you:

Create a Test Run (POST /test/runs)

Update test outcomes (PATCH /test/runs/{runId}/results)

Query Test Points to map automated results back to Test Case IDs

Authentication from Python Microsoft provides official docs on calling Azure DevOps REST APIs with Personal Access Tokens (PATs) . For Python, you can use requests with Basic Auth (username = "", password = PAT).

Example Python workflow (high-level)

import requests from requests.auth import HTTPBasicAuth org = "your-org" project = "your-project" pat = "your-pat" auth = HTTPBasicAuth("", pat) base_url = f"https://dev.azure.com/{org}/{project}/_apis/test" # 1. Create a Test Run run_url = f"{base_url}/runs?api-version=7.2-preview.3" run_data = {"name": "Automated Run - Regression", "plan": {"id": test_plan_id}} run = requests.post(run_url, json=run_data, auth=auth).json() run_id = run["id"] # 2. Map JUnit test cases -> Test Case IDs (from your mapping file) results = [] for junit_case in parsed_junit: case_id = mapping[junit_case["name"]] results.append({ "testCase": {"id": case_id}, "outcome": "Passed" if junit_case["status"] == "success" else "Failed" }) # 3. Publish results to the Test Run results_url = f"{base_url}/runs/{run_id}/results?api-version=7.2-preview.6" requests.post(results_url, json=results, auth=auth)

This example assumes you maintain a mapping file (e.g., JSON/CSV) where JUnit <testcase name="..."> corresponds to a Test Case ID in Azure Test Plans.

Recommended next steps

Use the Test Points API to dynamically retrieve Test Point IDs if you don’t want to maintain a static mapping.

Wrap your script in a pipeline task so it runs after your JUnit tests are complete.

Start with a small subset of cases to validate the mapping before rolling out across your 1,000+ regression cases.

Hope this helps you! If you find this helpful, please do consider upvote and accept the answer. Thank you!
Martin Bečka 25 Reputation points

2025-09-09T08:49:50.2766667+00:00

Hi, thanks for the tips!

You’ve been a great help.

Best regards, Martin

Share via

Displaying Tags from JUnit XML in Azure DevOps Test Results

0 additional answers

Your answer