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]> 2738cbb
  • Loading branch information
SeanKilleen committed Feb 7, 2025
1 parent e3c9fdb commit 3200721
Show file tree
Hide file tree
Showing 4 changed files with 737 additions and 725 deletions.
18 changes: 14 additions & 4 deletions articles/vs-test-adapter/AdapterV4-Release-Notes.html
Original file line number Diff line number Diff line change
Expand Up @@ -12,9 +12,9 @@
gtag('config', 'G-PCB5BYBNM2');
</script>
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
<title>Adapter V4 Release Notes | NUnit Docs </title>
<title>Adapter Release Notes | NUnit Docs </title>
<meta name="viewport" content="width=device-width">
<meta name="title" content="Adapter V4 Release Notes | NUnit Docs ">
<meta name="title" content="Adapter Release Notes | NUnit Docs ">


<link rel="shortcut icon" href="../../favicon.ico">
Expand Down Expand Up @@ -84,11 +84,21 @@
<div class="article row grid-right">
<div class="col-md-10">
<article class="content wrap" id="_content" data-uid="">
<h1 id="adapter-v4-release-notes">Adapter V4 Release Notes</h1>
<h1 id="adapter-release-notes">Adapter Release Notes</h1>

<h2 id="nunit3-test-adapter-for-visual-studio-and-dotnet---version-500---february-7-2025">NUnit3 Test Adapter for Visual Studio and Dotnet - Version 5.0.0 - February 7, 2025</h2>
<p>This major release introduce support for the new Microsoft Testing Platform.</p>
<h3 id="enhancements">Enhancements</h3>
<ul>
<li><a href="https://github.com/nunit/nunit3-vs-adapter/issues/1152">1152</a> Microsoft Testing Platform for NUnit</li>
</ul>
<p>See more information <a href="https://docs.nunit.org/articles/vs-test-adapter/NUnit-And-Microsoft-Test-Platform.html">here</a></p>
<h3 id="breaking-changes">Breaking changes</h3>
<p>Althought this is a major version, there is no direct breaking changes when using it without enabling the MTP.
Using it <strong>with</strong> MTP enabled will change some parts of how to use it, see the documentation for details.</p>
<h2 id="nunit3-test-adapter-for-visual-studio-and-dotnet---version-460---july-26-2024">NUnit3 Test Adapter for Visual Studio and Dotnet - Version 4.6.0 - July 26, 2024</h2>
<p>There are 10 issues fixed in this release.</p>
<h3 id="enhancements">Enhancements</h3>
<h3 id="enhancements-1">Enhancements</h3>
<ul>
<li><a href="https://github.com/nunit/nunit3-vs-adapter/issues/1138">1138</a> Add partition filter parsing to the adapter.</li>
<li><a href="https://github.com/nunit/nunit3-vs-adapter/issues/1114">1114</a> Is test result file creation now supported by NUnit
Expand Down
22 changes: 12 additions & 10 deletions articles/vs-test-adapter/NUnit-And-Microsoft-Test-Platform.html
Original file line number Diff line number Diff line change
Expand Up @@ -87,12 +87,12 @@
<h1 id="nunit-and-microsoft-test-platform">NUnit and Microsoft Test Platform</h1>

<h2 id="overview">Overview</h2>
<p>Microsoft Test Platform (MTP) is the new platform for testing from Microsoft. Test projects can be run as
executables, as with <a href="../nunit/running-tests/NUnitLite-Runner.html">NUnitLite</a> currently. There is no longer a test
runner; the executable <em>is</em> the test runner.</p>
<p>Microsoft Test Platform (MTP) is the new platform for testing from Microsoft. Test projects can be run as executables,
as with <a href="../nunit/running-tests/NUnitLite-Runner.html">NUnitLite</a> currently. There is no longer a test runner; the
executable <em>is</em> the test runner.</p>
<p>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.</p>
the NUnit3TestAdapter contains what is necessary to run the MTP using the existing test runners.</p>
<p>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.</p>
<h2 id="changing-a-project-to-use-mtp">Changing a Project to Use MTP</h2>
Expand All @@ -105,18 +105,20 @@ <h2 id="changing-a-project-to-use-mtp">Changing a Project to Use MTP</h2>
</code></pre>
<p>The first property, <code>EnableNUnitRunner</code>, 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 <code>dotnet test</code>.</p>
<h2 id="switching-from-vstest-to-dotnet-test">Switching from VSTest to dotnet test</h2>
<p>You can switch between <code>VSTest</code> and <code>dotnet test</code> using a property in your csproj (or Directory.Build.props):</p>
<pre><code class="lang-xml"> &lt;TestingPlatformDotnetTestSupport&gt;true&lt;/TestingPlatformDotnetTestSupport&gt;
</code></pre>
<p>See <a href="https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-integration-dotnet-test#dotnet-test---microsofttestingplatform-mode">this article</a>
for more information.</p>
<h2 id="information-on-the-microsoft-test-platform">Information on the Microsoft Test Platform</h2>
<ul>
<li><a href="https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-intro?tabs=dotnetcli">Microsoft Test Platform</a></li>
<li><a href="https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-integration-dotnet-test">Use Microsoft.Testing.Platform with dotnet test</a></li>
<li><a href="https://learn.microsoft.com/en-us/dotnet/core/testing/unit-testing-platform-architecture">Microsoft Test Platform Architecture</a></li>
<li><a href="https://github.com/nunit/nunit3-vs-adapter.issues/tree/master/Issue1152">NUnit Samples</a></li>
<li><a href="https://github.com/nunit/nunit3-vs-adapter/issues/1152">Adapter issue for implementing MTP</a></li>
</ul>
<h2 id="known-issues">Known issues</h2>
<p>In the current (v5) version of the NUnit3TestAdapter, running single tests doesn't work. It will always run all tests.
See <a href="https://github.com/nunit/nunit3-vs-adapter/issues/1232">Adapter Issue 1232</a>.</p>
<p>This applies to both Test Explorer and <code>dotnet test</code>.</p>
<p>As a workaround for the latter, you can filter tests using MTP-specific commands
like <code>dotnet test -- --filter Name=Test1</code>.</p>

</article>
</div>
Expand Down
Loading

0 comments on commit 3200721

Please sign in to comment.