Skip to content

Commit

Permalink
Release adapter V5 (#1014)
Browse files Browse the repository at this point in the history
* Release adapter V5

* fix line length

* Add link

* word choice

* on second thought, remove link

---------

Co-authored-by: Sean Killeen <[email protected]>
  • Loading branch information
OsirisTerje and SeanKilleen authored Feb 7, 2025
1 parent e0b5d9f commit 2738cbb
Show file tree
Hide file tree
Showing 2 changed files with 33 additions and 15 deletions.
17 changes: 16 additions & 1 deletion docs/articles/vs-test-adapter/AdapterV4-Release-Notes.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,19 @@
# Adapter V4 Release Notes
# Adapter Release Notes

## NUnit3 Test Adapter for Visual Studio and Dotnet - Version 5.0.0 - February 7, 2025

This major release introduce support for the new Microsoft Testing Platform.

### Enhancements

* [1152](https://github.com/nunit/nunit3-vs-adapter/issues/1152) Microsoft Testing Platform for NUnit

See more information [here](https://docs.nunit.org/articles/vs-test-adapter/NUnit-And-Microsoft-Test-Platform.html)

### Breaking changes

Althought this is a major version, there is no direct breaking changes when using it without enabling the MTP.
Using it **with** MTP enabled will change some parts of how to use it, see the documentation for details.

## NUnit3 Test Adapter for Visual Studio and Dotnet - Version 4.6.0 - July 26, 2024

Expand Down
31 changes: 17 additions & 14 deletions docs/articles/vs-test-adapter/NUnit-And-Microsoft-Test-Platform.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,13 +2,13 @@

## Overview

Microsoft Test Platform (MTP) is the new platform for testing from Microsoft. Test projects can be run as
executables, as with [NUnitLite](../nunit/running-tests/NUnitLite-Runner.md) currently. There is no longer a test
runner; the executable _is_ the test runner.
Microsoft Test Platform (MTP) is the new platform for testing from Microsoft. Test projects can be run as executables,
as with [NUnitLite](../nunit/running-tests/NUnitLite-Runner.md) currently. There is no longer a test runner; the
executable _is_ the test runner.

It will take time to develop feature parity with NUnit's current system, and there are many historical factors to
consider. But, the NUnit team recognizes that in the meantime, there needs to be a bridge between these two. In NUnit,
the NUnit3TestAdapter contains what is necessary to run the MTP using the same old test runners.
the NUnit3TestAdapter contains what is necessary to run the MTP using the existing test runners.

This means we have two modes of MTP operation: either use the new platform but not as an executable, or use it
as an executable too.
Expand All @@ -30,18 +30,21 @@ In a property group (use the top-level one), add the following two properties:
The first property, `EnableNUnitRunner`, enables the MTP. The second enables it to also run as an executable (but it
doesn't prevent you from using it in Test Explorer or through `dotnet test`.

## Information on the Microsoft Test Platform
## Switching from VSTest to dotnet test

* [Microsoft Test Platform](https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-intro?tabs=dotnetcli)
* [NUnit Samples](https://github.com/nunit/nunit3-vs-adapter.issues/tree/master/Issue1152)
* [Adapter issue for implementing MTP](https://github.com/nunit/nunit3-vs-adapter/issues/1152)
You can switch between `VSTest` and `dotnet test` using a property in your csproj (or Directory.Build.props):

## Known issues
```xml
<TestingPlatformDotnetTestSupport>true</TestingPlatformDotnetTestSupport>
```

In the current (v5) version of the NUnit3TestAdapter, running single tests doesn't work. It will always run all tests.
See [Adapter Issue 1232](https://github.com/nunit/nunit3-vs-adapter/issues/1232).
See [this article](https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-integration-dotnet-test#dotnet-test---microsofttestingplatform-mode)
for more information.

This applies to both Test Explorer and `dotnet test`.
## Information on the Microsoft Test Platform

As a workaround for the latter, you can filter tests using MTP-specific commands
like `dotnet test -- --filter Name=Test1`.
* [Microsoft Test Platform](https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-intro?tabs=dotnetcli)
* [Use Microsoft.Testing.Platform with dotnet test](https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-integration-dotnet-test)
* [Microsoft Test Platform Architecture](https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-architecture)
* [NUnit Samples](https://github.com/nunit/nunit3-vs-adapter.issues/tree/master/Issue1152)
* [Adapter issue for implementing MTP](https://github.com/nunit/nunit3-vs-adapter/issues/1152)

0 comments on commit 2738cbb

Please sign in to comment.