Skip to main content
Microsoft.TeamFoundation.PublishTestResults package icon

Microsoft.TeamFoundation.PublishTestResults

This task can be used to Publish test results and upload test attachments on Azure DevOps The following results formats are supported with this package- 1) JUnit - publish tests from Junit projects 2) NUnit- publish tests from Nunit projects 3) VSTest- publish tests from Visual Studio projects 4) Xunit- publish tests from Xunit projects Publish Test Results is supported for both TFS and Azure DevOps with attachments

Total Downloads
242.6K
242,591
Published
May 7, 2026
Latest stable version

Install

.NET CLI
dotnet add package Microsoft.TeamFoundation.PublishTestResults --version 20.271.1-preview
Package Manager Console
Install-Package Microsoft.TeamFoundation.PublishTestResults -Version 20.271.1-preview
PackageReference
<PackageReference Include="Microsoft.TeamFoundation.PublishTestResults" Version="20.271.1-preview" />

Frameworks

.NETFramework4.7.2 .NETStandard2.0

Dependencies

[5.2.7, )
[11.2.3, )
[11.2.3, )
[2.0.5, )
[11.2.3, )
[20.271.1-preview, 20.271.1-preview]
Newtonsoft.Json
.NETFramework4.7.2
[13.0.4, )
[5.2.7, )
[11.2.3, )
[11.2.3, )
[2.0.5, )
[11.2.3, )
[20.271.1-preview, 20.271.1-preview]
Newtonsoft.Json
.NETStandard2.0
[13.0.4, )
[4.3.0, )

Adoption guide

A verified publisher signal is available. Assess fit from the package's supported frameworks, license and dependency graph rather than popularity alone.

This version is marked prerelease. Validate its API and upgrade path before production use.

No SPDX license expression is published. Review the license text and your organisation's policy before redistribution.

Compatibility metadata lists 2 target frameworks; confirm the exact target used by your application.

The published metadata declares 15 direct dependency entries across framework groups. Inspect the resolved dependency graph for your target framework.

How to read this guidance

Sources: published NuGet v3 registry metadata and explicit NuBrowse editorial guides. Refresh: package metadata is refreshed from NuGet when the page loads. Limit: this is not a security, legal or compatibility guarantee; validate the selected version in your project.

Useful next steps

Move from package metadata to a concrete selection or review workflow.