diff --git a/docs/articles/nunit/writing-tests/attributes/explicit.md b/docs/articles/nunit/writing-tests/attributes/explicit.md index 7f9ab8254..ac41bd85c 100644 --- a/docs/articles/nunit/writing-tests/attributes/explicit.md +++ b/docs/articles/nunit/writing-tests/attributes/explicit.md @@ -61,6 +61,17 @@ included, the test is a non-explicit testrun, and all explicit tests will be ign can be empty, or even have a false Assume statement, which will make the test be inconclusive, thus not part of your results."* +## TRICK + +If you want to ensure NO Explicit tests are being run, e.g. a CI build, you can change the ExplicitMode to None. +You can do this either in a .runsettings file, or as a command line parameter + +```cmd +dotnet test -- NUnit.ExplicitMode=None +``` + +(From version 5.2.0) + ## Test Fixture Syntax C#: diff --git a/docs/articles/vs-test-adapter/Adapter-Engine-Compatibility.md b/docs/articles/vs-test-adapter/Adapter-Engine-Compatibility.md index 43697d6b3..75ad11e6f 100644 --- a/docs/articles/vs-test-adapter/Adapter-Engine-Compatibility.md +++ b/docs/articles/vs-test-adapter/Adapter-Engine-Compatibility.md @@ -15,6 +15,8 @@ post. | Adapter version | Embedded engine version | | --------------- | ----------------------- | +| 5.2.0 | 3.18.1 | +| 5.1.0 | 3.18.1 | | 5.0.0 | 3.18.1 | | 4.6.0 | 3.18.1 | | 4.5.0 | 3.15.4 | diff --git a/docs/articles/vs-test-adapter/Adapter-License.md b/docs/articles/vs-test-adapter/Adapter-License.md index 0532d7533..14e566240 100644 --- a/docs/articles/vs-test-adapter/Adapter-License.md +++ b/docs/articles/vs-test-adapter/Adapter-License.md @@ -2,7 +2,7 @@ ## MIT License -Copyright (c) 2011-2021 Charlie Poole, 2014-2023 Terje Sandstrom +Copyright (c) 2011-2021 Charlie Poole, 2014-2025 Terje Sandstrom Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal diff --git a/docs/articles/vs-test-adapter/AdapterV4-Release-Notes.md b/docs/articles/vs-test-adapter/AdapterV4-Release-Notes.md index ee27da230..ba778146f 100644 --- a/docs/articles/vs-test-adapter/AdapterV4-Release-Notes.md +++ b/docs/articles/vs-test-adapter/AdapterV4-Release-Notes.md @@ -7,6 +7,50 @@ uid: adapterreleasenotes # Adapter Release Notes +## NUnit3 Test Adapter for Visual Studio and Dotnet - Version 5.2.0 - October 6, 2025 + +There are 2 issues fixed in this release. + +In addition, the MTP version have been updated to 1.9.0. + +### Enhancements + +* [1111](https://github.com/nunit/nunit3-vs-adapter/issues/1111) New Mode that completely excludes explicit tests. Thanks to NUnit Team member [Terje Sandstrom](https://github.com/OsirisTerje) for [PR 1323](https://github.com/nunit/nunit3-vs-adapter/pull/1323) + +### Bug fixes + +* [1292](https://github.com/nunit/nunit3-vs-adapter/issues/1292) (Apparently) inconsistent version requirements of Microsoft.Testing.Extensions.VSTestBridge and Microsoft.Testing.Platform.MSBuild. Thanks to NUnit Team member [Terje Sandstrom](https://github.com/OsirisTerje) for [PR 1296](https://github.com/nunit/nunit3-vs-adapter/pull/1296) + +### Acknowledgements + +We want to express our heartfelt gratitude to everyone who has contributed to this release +by reporting bugs, suggesting enhancements, and providing valuable feedback. +Your efforts help make NUnit better for the entire community. + +A special thank you to the following reporters for identifying issues: + + + + + + + +
dmurtyLennart BrggemannTerje Sandstrom
+ +and to the commenters who engaged in discussions and offered further insights: + + + + + + + + + + + +
dmurtyManfred BrandsMohamed HassanTerje Sandstrom
Youssef Victor
+ ## NUnit3 Test Adapter for Visual Studio and Dotnet - Version 5.1.0 - August 6, 2025 There are 10 issues fixed in this release. diff --git a/docs/articles/vs-test-adapter/Tips-And-Tricks.md b/docs/articles/vs-test-adapter/Tips-And-Tricks.md index daebc957e..29241ea16 100644 --- a/docs/articles/vs-test-adapter/Tips-And-Tricks.md +++ b/docs/articles/vs-test-adapter/Tips-And-Tricks.md @@ -44,7 +44,7 @@ Certain NUnit Test Adapter settings are configurable using a .runsettings file. | [NewOutputXmlFileForEachRun](#newoutputxmlfileforeachrun) | bool | Creates a new file for each test run | false | | [IncludeStackTraceForSuites](#includestacktraceforsuites) | bool | Includes stack trace for failures in suites, like exceptions in OneTimeSetup and OneTimeTearDown | true | | [IncludeStackTrace](#includestacktrace) | bool | Includes stack trace for all failures | true | -| [ExplicitMode](#explicitmode) | enum | Changes handling of explicit tests, options are `Strict` or `Relaxed` | Strict | +| [ExplicitMode](#explicitmode) | enum | Changes handling of explicit tests, options are `Strict`, `Relaxed` or `None` | Strict | | [SkipExecutionWhenNoTests](#skipexecutionwhennotests) | bool | Skip execution if no tests are found | false | | [AllowParallelWithDebugger](#allowparallelwithdebugger) | bool | Allow parallel execution when debugger is attached | false | | [ThrowOnEachFailureUnderDebugger](#throwoneachfailureunderdebugger) | bool | | false | @@ -364,7 +364,7 @@ This is default true. If turned off (false) it will stop outputting any stacktr #### ExplicitMode -This setting can be either ```Strict``` or ```Relaxed```. The default is ```Strict```, which means that ```Explicit``` +This setting can be either ```Strict```, ```Relaxed``` or ```None```. The default is ```Strict```, which means that ```Explicit``` tests can only be run with other Explicit tests, and not mixed with non-Explicit tests. The ```Relaxed``` mode is the original NUnit mode, where if you select a category, a class or a set of tests, both explicit and non-explicit tests will be run. From Visual Studio Test Explorer there are no longer (since VS2019) any way of separating between a @@ -373,6 +373,10 @@ line tests, dependent upon how your tests are set up and run. (From version 4.2.0) +When using `None`, no explicit tests will be run at all. This can be useful for CI scenarios. + +(From version 5.2.0) + #### SkipExecutionWhenNoTests If set, this setting will skip execution for an assembly if no tests are found during the pre-execution discovery phase.