NUnit Console and Engine 3.12.0-beta1

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!

See the Release Notes for a full list of changes.

NUnit Console and Engine 3.11.1

This hotfix fixes a problem with NUnit Project file settings being ignored.

See the Release Notes for details.

NUnit Console and Engine 3.11

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.

See the Release Notes for a full list of changes.

NUnit Console and Engine 3.10

This 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.

See the Release Notes for a full list of changes.

NUnit Console and Engine 3.9

This 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 predictible.

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.

See the Release Notes for a full list of changes.

NUnit Console and Engine 3.8

This release includes several fixes when unloading AppDomains and better error reporting. The
aggregate NuGet packages also include updated versions of several extensions.

See the Release Notes for a full list of changes.

NUnit Console and Engine 3.7

Engine

• Creates a .NET Standard version of the engine for use in the Visual Studio Adapter
• Fixes several issues that caused the runner to exit with a SocketException

NUnit .NET Standard Engine v3.7 alpha 1

This is the first release of a .NET Standard version of the engine for use in Visual Studio Adapter.

NUnit Console 3.6.1

This hotfix release addresses a race condition in the Engine that caused tests to intermittently fail.

NUnit Console 3.6

Console Runner

• Added command line option --skipnontestassemblies to skip assemblies that do
  not contain tests without raising an error and to skip assemblies that contain
  the NUnit.Framework.NonTestAssemblyAttribute.
• Messages from the new Multiple Assert blocks will be displayed individually
• Warnings from the new Warn.If, Warn.Unless and Assert.Warn are now displayed

Engine

• NUnit agents now monitor the running engine process and will terminate themselves
  if the parent runner process is killed or dies