You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/articles/vs-test-adapter/AdapterV4-Release-Notes.md
+68Lines changed: 68 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,74 @@ uid: adapterreleasenotes
7
7
8
8
# Adapter Release Notes
9
9
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:
Copy file name to clipboardExpand all lines: docs/articles/vs-test-adapter/Tips-And-Tricks.md
+13-4Lines changed: 13 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,12 +42,13 @@ Certain NUnit Test Adapter settings are configurable using a .runsettings file.
42
42
|[DiscoveryMethod](#discoverymethod)| enum | How execution discovery is done, options are `Legacy` or `Current`| Current |
43
43
|[AssemblySelectLimit](#assemblyselectlimit)| int | Number of tests accepted before filters are turned off | 2000 |
44
44
|[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 |
48
48
|[SkipExecutionWhenNoTests](#skipexecutionwhennotests)| bool | Skip execution if no tests are found | false |
49
49
|[AllowParallelWithDebugger](#allowparallelwithdebugger)| bool | Allow parallel execution when debugger is attached | false |
|[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 |
51
52
52
53
### Visual Studio templates for runsettings
53
54
@@ -399,6 +400,14 @@ is attached. The default is `false`.
399
400
400
401
(From version 4.6, require NUnit from 4.2)
401
402
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.
0 commit comments