<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/microsoft-testing-platform-github-and-azure-devops-reporting-pe6wqvpos" -->

---
title: Microsoft Testing Platform GitHub and Azure DevOps Reporting
description: Microsoft Testing Platform now includes new libraries for publishing test result reports directly in GitHub Actions and Azure DevOps Pipelines, reducing the...
canonical: https://daily.dev/posts/microsoft-testing-platform-github-and-azure-devops-reporting-pe6wqvpos
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Microsoft Testing Platform GitHub and Azure DevOps Reporting | daily.dev
og:description: Microsoft Testing Platform now includes new libraries for publishing test result reports directly in GitHub Actions and Azure DevOps Pipelines, reducing the...
og:url: https://daily.dev/posts/microsoft-testing-platform-github-and-azure-devops-reporting-pe6wqvpos
og:image: https://api.daily.dev/og/posts/pe6WQvpos.png
og:image:alt: Microsoft Testing Platform GitHub and Azure DevOps Reporting
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Microsoft Testing Platform GitHub and Azure DevOps Reporting

**[We Are .NET](https://daily.dev/sources/wearedotnet)** · 4 min read · 2 upvotes · 0 comments

## Summary

Microsoft Testing Platform now includes new libraries for publishing test result reports directly in GitHub Actions and Azure DevOps Pipelines, reducing the need for manual reporting steps. The Microsoft.Testing.Extensions.AzureDevOpsReport and Microsoft.Testing.Extensions.GitHubActionsReport (pre-release) NuGet packages enable new CLI flags like --report-gh, --report-azdo, --publish-azdo-test-results, and --report-azdo-upload-artifacts files. A walkthrough using TUnit shows how to wire these into pipeline configs, including a workaround for a current ObjectDisposedException bug in Azure DevOps reporting that requires the --diagnostic flag, expected to be fixed in reporter version 2.3.4. Code coverage tab population in Azure DevOps still requires the separate PublishCodeCoverageResults@2 task.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://blog.ostebaronen.dk/2026/08/mtp-reporting.html>

## Questions this post answers

### How do I publish .NET test results to Azure DevOps using Microsoft Testing Platform without a separate PublishTestResults task?

Install the Microsoft.Testing.Extensions.AzureDevOpsReport package and run dotnet test with the flags --report-azdo, --publish-azdo-test-results, and --report-azdo-upload-artifacts files. This streams results into the Test tab, adds PR comments, and uploads artifacts. You also need to pass a System.AccessToken via the SYSTEM_ACCESSTOKEN environment variable for uploads to work.

_daily.dev surfaces practical CI setup notes like these for teams wiring up .NET test reporting pipelines._

### Why does Microsoft Testing Platform Azure DevOps reporting throw an ObjectDisposedException?

A known bug in the current Azure DevOps reporting extension causes an ObjectDisposedException and fails tests unless the --diagnostic flag is added to the dotnet test command. This workaround is required until reporter version 2.3.4 ships, which is expected to fix the underlying issue.

_Track workarounds like this on daily.dev before a broken test pipeline costs you a debugging session._

### What flag enables GitHub Actions summary reporting for .NET tests run with Microsoft Testing Platform?

The --report-gh flag, enabled by installing the Microsoft.Testing.Extensions.GitHubActionsReport package (currently pre-release), publishes a test results summary directly on GitHub Actions workflow runs. It can be combined with third-party CTRF reporting tools like ctrf-io/github-test-reporter for PR comments without conflict.

_Developers picking test reporting tools for GitHub Actions can follow updates like this via daily.dev._

## Similar posts on daily.dev

- [Microsoft.Testing.Platform Now Fully Supported in Azure DevOps](https://daily.dev/posts/microsoft-testing-platform-now-fully-supported-in-azure-devops-bhgc8b7g8) · DevBlogs · 0 upvotes · 0 comments
- [Test reporting in Microsoft.Testing.Platform: from red build to root cause](https://daily.dev/posts/test-reporting-in-microsoft-testing-platform-from-red-build-to-root-cause-8w2taxpcg) · .NET Blog · 0 upvotes · 0 comments
- [xUnit.v3 4.0.0 released](https://daily.dev/posts/xunit-v3-4-0-0-released-uye7e4ug8) · We Are .NET · 2 upvotes · 0 comments

---

Tags: [#cicd](https://daily.dev/tags/cicd), [#.net](https://daily.dev/tags/.net), [#github-actions](https://daily.dev/tags/github-actions), [#azure-devops](https://daily.dev/tags/azure-devops)

[View this post on daily.dev](https://daily.dev/posts/microsoft-testing-platform-github-and-azure-devops-reporting-pe6wqvpos)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"Microsoft Testing Platform GitHub and Azure DevOps Reporting","url":"https://daily.dev/posts/microsoft-testing-platform-github-and-azure-devops-reporting-pe6wqvpos","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/microsoft-testing-platform-github-and-azure-devops-reporting-pe6wqvpos"},"datePublished":"2026-08-14T12:37:15.307Z","dateModified":"2026-09-14T08:36:29.421Z","description":"Microsoft Testing Platform now includes new libraries for publishing test result reports directly in GitHub Actions and Azure DevOps Pipelines, reducing the...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c38254095a73545810f34c33b09ace93?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/c38254095a73545810f34c33b09ace93?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"We Are .NET","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"We Are .NET","logo":"https://media.daily.dev/image/upload/s--BsnVOa3i--/f_auto/v1718347410/logos/wearedotnet","url":"https://daily.dev/sources/wearedotnet"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/microsoft-testing-platform-github-and-azure-devops-reporting-pe6wqvpos","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"cicd,.net,github-actions,azure-devops","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"We Are .NET","item":"https://daily.dev/sources/wearedotnet"},{"@type":"ListItem","position":3,"name":"Microsoft Testing Platform GitHub and Azure DevOps Reporting"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/microsoft-testing-platform-github-and-azure-devops-reporting-pe6wqvpos#faq","mainEntity":[{"@type":"Question","name":"How do I publish .NET test results to Azure DevOps using Microsoft Testing Platform without a separate PublishTestResults task?","acceptedAnswer":{"@type":"Answer","text":"Install the Microsoft.Testing.Extensions.AzureDevOpsReport package and run dotnet test with the flags --report-azdo, --publish-azdo-test-results, and --report-azdo-upload-artifacts files. This streams results into the Test tab, adds PR comments, and uploads artifacts. You also need to pass a System.AccessToken via the SYSTEM_ACCESSTOKEN environment variable for uploads to work. daily.dev surfaces practical CI setup notes like these for teams wiring up .NET test reporting pipelines."}},{"@type":"Question","name":"Why does Microsoft Testing Platform Azure DevOps reporting throw an ObjectDisposedException?","acceptedAnswer":{"@type":"Answer","text":"A known bug in the current Azure DevOps reporting extension causes an ObjectDisposedException and fails tests unless the --diagnostic flag is added to the dotnet test command. This workaround is required until reporter version 2.3.4 ships, which is expected to fix the underlying issue. Track workarounds like this on daily.dev before a broken test pipeline costs you a debugging session."}},{"@type":"Question","name":"What flag enables GitHub Actions summary reporting for .NET tests run with Microsoft Testing Platform?","acceptedAnswer":{"@type":"Answer","text":"The --report-gh flag, enabled by installing the Microsoft.Testing.Extensions.GitHubActionsReport package (currently pre-release), publishes a test results summary directly on GitHub Actions workflow runs. It can be combined with third-party CTRF reporting tools like ctrf-io/github-test-reporter for PR comments without conflict. Developers picking test reporting tools for GitHub Actions can follow updates like this via daily.dev."}}]}
```