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.
Questions this post answers
How do I publish .NET test results to GitHub Actions summaries without a third-party action?
Install the Microsoft.Testing.Extensions.GitHubActionsReport NuGet package and run dotnet test with the --report-gh flag. This publishes a summary directly on the GitHub Actions workflow run without needing an external action like ctrf-io/github-test-reporter, though that package is still pre-release. daily.dev surfaces practical CI/CD reporting guides like this for teams wiring up .NET test pipelines.
Why does Azure DevOps reporting from Microsoft Testing Platform throw an ObjectDisposedException?
There is a known bug where Azure DevOps reporting fails tests with an ObjectDisposedException unless the --diagnostic flag is also passed to dotnet test. This is a temporary workaround; the issue is expected to be fixed in the next version of the reporter, 2.3.4. Developers tracking tooling bugs like this rely on daily.dev to catch fixes before they hit production pipelines.
What CLI flags does Microsoft.Testing.Extensions.AzureDevOpsReport add for dotnet test?
It adds --report-azdo to add log entries and pull request comments, --publish-azdo-test-results to stream results into the Test tab on a pipeline run, and --report-azdo-upload-artifacts files to upload test results and code coverage as pipeline artifacts, though the latter doesn't populate the Test or Coverage tabs. Configuring Azure DevOps test reporting gets easier when developers compare flag behavior on daily.dev.