Skip to content

Commit ad47c4d

Browse files
authored
Merge pull request #1126 from nunit/adapter61
Added release information for adapter version 6.1
2 parents ebce976 + 80341cb commit ad47c4d

File tree

5 files changed

+89
-9
lines changed

5 files changed

+89
-9
lines changed

docs/articles/vs-test-adapter/Adapter-Engine-Compatibility.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,7 @@ post.
1515

1616
| Adapter version | Embedded engine version |
1717
| --------------- | ----------------------- |
18+
| 6.1.0 | 3.22.0 |
1819
| 6.0.1 | 3.21.1 |
1920
| 6.0.0 | 3.21.0 |
2021
| 5.2.0 | 3.18.1 |

docs/articles/vs-test-adapter/AdapterV4-Release-Notes.md

Lines changed: 68 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,74 @@ uid: adapterreleasenotes
77

88
# Adapter Release Notes
99

10+
## NUnit3 Test Adapter for Visual Studio and Dotnet - Version 6.1.0 - January 7, 2026
11+
12+
This is a bug-fix release that addresses a series of issues related to assembly loading.
13+
It also introduces several new settings. One of these, `UseDefaultAssemblyLoadContext`, is crucial for correct assembly loading and is now enabled by default by the adapter.
14+
15+
The remaining settings are intended for development and diagnostics. `DebugEngine` enables debugging of the NUnit Engine, and `InternalTraceLevel` allows the engine’s internal trace level to be configured and is now passed through to the engine.
16+
17+
### Bug fixes
18+
19+
* [1393](https://github.com/nunit/nunit3-vs-adapter/issues/1393) System.IO.FileNotFoundException: Could not load file or assembly 'System.Text.Json, Version=10.0.0.0.
20+
* [1391](https://github.com/nunit/nunit3-vs-adapter/issues/1391) NUnit3TestAdapter V6.0.1 doesn't work with Resharpers Unit Tests explorer.
21+
* [1390](https://github.com/nunit/nunit3-vs-adapter/issues/1390) I am getting a System.InvalidCastException when updating from NUnit3TestAdapter Version=5.2.0 to 6.0.1.
22+
* [1389](https://github.com/nunit/nunit3-vs-adapter/issues/1389) Double loading assemblys NUnit3TestAdapter 6.0.1 with Microsoft Testing Platform (MTP). Fixed by [PR 1395](https://github.com/nunit/nunit3-vs-adapter/pull/1395)
23+
* [1375](https://github.com/nunit/nunit3-vs-adapter/issues/1375) New failures in dynamic code evaluation in v6. Fixed by [PR 1395](https://github.com/nunit/nunit3-vs-adapter/pull/1395)
24+
* [1348](https://github.com/nunit/nunit3-vs-adapter/issues/1348) [MTP] AwesomeAssertions throws different NUnit.Framework.AssertionException than expected at runtime.
25+
26+
### Breaking changes
27+
28+
The 6.1 version of the adapter use the NUnit.Engine version 3.22.0. This version introduce a changed way of loading assemblies.
29+
In order for the adapter to handle MTP (Microsoft test Platform) it needs to use the default loading context, which the engine may not use.
30+
The introduction of the `UseDefaultAssemblyLoadContext` ensures this works.
31+
The current versions of Resharper and Rider (2025.3.1) however do not yet support the `UseDefaultAssemblyLoadContext`, and therefore the user **may** experience assembly loading issues.
32+
33+
If you're not using Visual Studio test explorer, but only Rider or Resharper's, they will work if you don't install the adapter.
34+
35+
### Acknowledgements
36+
37+
We want to express our heartfelt gratitude to everyone who has contributed to this release
38+
by reporting bugs, suggesting enhancements, and providing valuable feedback.
39+
Your efforts help make NUnit better for the entire community.
40+
41+
A special thank you to the following reporters for identifying issues:
42+
43+
<table>
44+
<tr>
45+
<td><a href="https://github.com/ScarletKuro">Artyom M.</a></td>
46+
<td><a href="https://github.com/cbersch">Christoph Bersch</a></td>
47+
<td><a href="https://github.com/glennawatson">Glenn Watson</a></td>
48+
<td><a href="https://github.com/MJB222398">MJB222398</a></td>
49+
</tr>
50+
<tr>
51+
<td><a href="https://github.com/Methuselah96">Nathan Bierema</a></td>
52+
<td><a href="https://github.com/Sveti86">Svetoslav Inkolov</a></td>
53+
</tr>
54+
</table>
55+
56+
and to the commenters who engaged in discussions and offered further insights:
57+
58+
<table>
59+
<tr>
60+
<td><a href="https://github.com/ScarletKuro">Artyom M.</a></td>
61+
<td><a href="https://github.com/bradford-fisher">Bradford Fisher</a></td>
62+
<td><a href="https://github.com/CharliePoole">CharliePoole</a></td>
63+
<td><a href="https://github.com/cbersch">Christoph Bersch</a></td>
64+
</tr>
65+
<tr>
66+
<td><a href="https://github.com/manfred-brands">Manfred Brands</a></td>
67+
<td><a href="https://github.com/MJB222398">MJB222398</a></td>
68+
<td><a href="https://github.com/Methuselah96">Nathan Bierema</a></td>
69+
<td><a href="https://github.com/nesc58">nesc58</a></td>
70+
</tr>
71+
<tr>
72+
<td><a href="https://github.com/Sveti86">Svetoslav Inkolov</a></td>
73+
<td><a href="https://github.com/OsirisTerje">Terje Sandstrom</a></td>
74+
<td><a href="https://github.com/Youssef1313">Youssef Victor</a></td>
75+
</tr>
76+
</table>
77+
1078
## NUnit3 Test Adapter for Visual Studio and Dotnet - Version 6.0.1 - December 20, 2025
1179

1280
This is a hotfix release for version 6.0.0 to handle issues related to loading assemblies.

docs/articles/vs-test-adapter/Debugging.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,14 @@ The symbols are:
2626
NUnit.DebugExecution
2727
NUnit.DebugDiscovery
2828
NUnit.Debug
29+
NUnit.DebugEngine # (From version 6.1)
2930
```
3031

31-
The last setting is equal to setting both of the two above.
32+
The `NUnit.Debug` is equal to setting both of the two above.
3233

33-
From command line, you can set these by adding
34+
The `NUnit.DebugEngine` enables debugging of the embedded NUnit.Engine.
35+
36+
From command line, you can set these by adding e.g.
3437

3538
```cmd
3639
dotnet test -- NUnit.DebugExecution=true

docs/articles/vs-test-adapter/Supported-Frameworks.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -18,9 +18,8 @@ The table below shows the supported adapter versions for a given framework versi
1818
|Net 7|4.3 - 5.X ||
1919
|Net 8+|Works with 4.3.2 and upwards||
2020

21-
The adapter is shipped with three different versions of the test framework. The first is the full framework version,
22-
which is used for .NET Framework based test projects. The second is the .NET version 6.0, which is used for .NET
23-
6.0, and the third is .NET 8.0 which is used for .net 7.0, 8.0, 9.0, 10.0 and upwards.
21+
The adapter is shipped with two different versions of the test framework. The first is the full framework version,
22+
which is used for .NET Framework based test projects. The second is the .NET (Core) version.
2423
The different versions of the adapter supports different versions of the test framework.
2524
The table above shows the supported versions.
2625

docs/articles/vs-test-adapter/Tips-And-Tricks.md

Lines changed: 13 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -42,12 +42,13 @@ Certain NUnit Test Adapter settings are configurable using a .runsettings file.
4242
| [DiscoveryMethod](#discoverymethod) | enum | How execution discovery is done, options are `Legacy` or `Current` | Current |
4343
| [AssemblySelectLimit](#assemblyselectlimit) | int | Number of tests accepted before filters are turned off | 2000 |
4444
| [NewOutputXmlFileForEachRun](#newoutputxmlfileforeachrun) | bool | Creates a new file for each test run | false |
45-
| [IncludeStackTraceForSuites](#includestacktraceforsuites) | bool | Includes stack trace for failures in suites, like exceptions in OneTimeSetup and OneTimeTearDown | true |
46-
| [IncludeStackTrace](#includestacktrace) | bool | Includes stack trace for all failures | true |
47-
| [ExplicitMode](#explicitmode) | enum | Changes handling of explicit tests, options are `Strict`, `Relaxed` or `None` | Strict |
45+
| [IncludeStackTraceForSuites](#includestacktraceforsuites) | bool | Includes stack trace for failures in suites, e.g.OneTimeSetup/OneTimeTearDown | true |
46+
| [IncludeStackTrace](#includestacktrace) | bool | Includes stack trace for all failures | true |
47+
| [ExplicitMode](#explicitmode) | enum | Changes handling of explicit tests, options are `Strict`, `Relaxed` or `None` | Strict |
4848
| [SkipExecutionWhenNoTests](#skipexecutionwhennotests) | bool | Skip execution if no tests are found | false |
4949
| [AllowParallelWithDebugger](#allowparallelwithdebugger) | bool | Allow parallel execution when debugger is attached | false |
50-
| [ThrowOnEachFailureUnderDebugger](#throwoneachfailureunderdebugger) | bool | | false |
50+
| [ThrowOnEachFailureUnderDebugger](#throwoneachfailureunderdebugger) | bool | Throw on each failure when debugger is attached | false |
51+
| [UseDefaultAssemblyLoadContext](#usedefaultassemblyloadcontext) | bool | Force the engine to use Default Loading Context, otherwise engine decide | true |
5152

5253
### Visual Studio templates for runsettings
5354

@@ -399,6 +400,14 @@ is attached. The default is `false`.
399400

400401
(From version 4.6, require NUnit from 4.2)
401402

403+
#### UseDefaultAssemblyLoadContext
404+
405+
Controls how the NUnit.Engine (from version 3.22.0) does assembly loading. Default is `true`, and cause the engine to
406+
load the assemblies into the default assembly loading context. This is mandatory for MTP.
407+
If set to `false`, the engine will load assemblies based on its own algorithm, also taking isolation into account.
408+
409+
(From version 6.1)
410+
402411
---
403412

404413
### Some further information on directories

0 commit comments

Comments
 (0)