docs/articles/nunit-engine/release-notes.md
This release adds support for .net 8 by adding a missing agent.
Note that the release is based on the 3.15.5 version.
A version of the 3.15 series supporting NUnit 4. This is also required for having an engine for a corresponding adapter release.
This release fixes several critical or high-priority bugs in the 3.16.0 release.
Further releases in the 3.x series were not anticipated after 3.15. However, since a number of new features and enhancements have been implemented, we are releasing version 3.16 of the engine and console runner.
This release incorporates support for executing tests under .NET 7.0. The runner itself is now built for .NET 4.6.2 rather than .NET 2.0. Substantial changes have been made in the location of dependencies when running under .NET Core.
Release primarily to correct a critical bug arising when .NET 7.0 is installed.
Note: There is no 3.15.1 release because a 3.15.1 package identical to 3.15.0 was accidentally uploaded to NuGet.org when 3.15 was released.
Final Release of NUnit ConsoleRunner 3.15.0. No changes from the beta1 Release.
Version 3.15.0 is expected to be the final release in the 3.x series.
Beta release of version 3.15.0 of the Console Runner. Both the standard runner and the dotnet CLI command are now able to run tests under .Net 6.0.
This release features a new agent for tests targeting .NET 5.0. In addition, automation of our publication and release process is now complete from creation of a draft release through releasing to production on GitHub. While this doesn't impact users directly, it will allow us to speed up the introduction of new features in coming releases.
This is the first release of the NUnit Console Runner, nunit3-console.exe, which allows running of both .NET Framework
and .NET Core tests, either separately or in combination. The nunit3-console.exe runner executes under the .NET
Framework but is able to launch .NET Core agents and communicate with them over a TCP connection.
A second major feature in this release is engine support for preemptive cancellation when the normal approach of requesting the test run to self-terminate doesn't work. This is an engine feature, available to any runners supporting cancellation.
This release contains various improvements to running tests on .NET Core and Mono, and changes to extension loading logic to allow the Engine to better support extensions which target multiple platforms. There are additionally a number of fixes to issues that were identified with 3.12 Beta 1. Please also be aware that this will be the last version of the NUnit Engine to support .NET Standard 1.6.
The .NET Core Console remains in Beta due to some unresolved dependency loading and framework targeting issues - contributions to fix these issues would be very welcome!
Code contributions in this release were included from Charlie Poole, Chris Maddock, Christian Bay, Eberhard Beilharz, Ed Ball, Joseph Musser, Manohar Singh, Mattias Cavigelli and Mikkel Nylander Bundgaard. Thank you to all those who contributed both in code, and otherwise.
Please note the below list includes only issues resolved between 3.12.0 Beta 1 and the final release. For those upgrading from 3.11.1 or earlier, please also see the Beta release notes.
This is the first beta release of the NUnit Console able to run .NET Core Tests. In addition to this, this release also contains a number of bug fixes, improvements when running on Mono and significant refactoring work towards the goal of creating an engine able to run tests on a wider range of .NET platforms.
We're particularly interested in this beta release being tested by users of the .NET Core console and users running tests on Mono. Please feedback any issues to the nunit-console repository.
The .NET Core Console is a separate executable to the original version, and can be found in either the .zip file download, or the new NUnit.ConsoleRunner.NetCore NuGet package. Our longer-term aim is to create a single console which is able to run both .NET Core and .NET Framework tests.
Code contributions in this release were included from Charlie Poole, Chris Maddock, Christian Bay, Eberhard Beilharz, Joseph Musser, Manohar Singh and Mikkel Nylander Bundgaard. Thank you to all those who contributed both in code, and other ways!
This hotfix fixes a problem with NUnit Project file settings being ignored.
This release fixes a range of minor bugs, and includes a significant amount of internal restructuring work. In future, this will enable improved .NET Standard support in the engine, and a .NET Core build of the console.
start-run data for ITestEventListenerThis release merges the .NET Standard version of the engine back into the nunit.engine NuGet package and adds a .NET
Standard 2.0 version of the engine that re-enables most services and extensions. This deprecates the
nunit.engine.netstandard NuGet package. Any test runners using the old .NET Standard version of the engine should
switch to this release.
The --params command line option which took multiple test parameters separated by a semicolon is now deprecated in
favor of the new --testparam command line option. One of the most common uses for test parameters was to pass
connection strings into tests but this required workarounds to handle the semicolons. Now you must pass in each test
parameter separately using a --testparam or --tp option for each.
--nocolorThis release should stop the dreaded SocketException problem on shutdown. The console also no longer returns -5 when AppDomains fail to unload at the end of a test run. These fixes should make CI runs much more stable and predictable.
For developers working on the NUnit Console and Engine project, Visual Studio 2017 update 5 or newer is now required to compile on the command line. This does not effect developers using NUnit or the NUnit Console, both of which support building and running your tests in any IDE and on any .NET Framework back to .NET 2.0.
repository metadata.This release includes several fixes when unloading AppDomains and better error reporting. The aggregate NuGet packages also include updated versions of several extensions.
noxml option--skipnontestassemblies to skip assemblies that do not contain tests without raising an
error and to skip assemblies that contain the NUnit.Framework.NonTestAssemblyAttribute.