NUnit Console and Engine 3.14.0

As part of this release we had 7 issues closed.

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.

Bugs

• #1012 Automatically roll-forward if no .NET Core 3.1 runtime available
• #1090 Test of --debug-agent option fails under linux Debug configuration

Build

• #570 Where are the checksums for your downloads?
• #1057 Automate all package publication and release
• #1075 Separate nunit.engine.core.tests from nunit.engine.tests
• #1084 Eliminate Packaging on Azure

Feature

• #1048 Agent for Net 5.0

Choosing a Package

The package nunit-console-runner.nupkg is a Chocolatey package and should be installed using choco.exe. It is also available at chocolatey.org. All other .nupkg packages are intended for use with nuget.exe and may be downloaded from nuget.org as well as here.

SHA256 Hashes of the release artifacts

• ad8f0e4f8bf305135b88e7040c18110015cb863e66880c9ff4fb46ac3c607489 NUnit.Console.3.14.0.nupkg
• 53cc270300202d4d04c302bdd3926c1de569a96ae56d9f542dd2fa4098b00d47 NUnit.ConsoleRunner.3.14.0.nupkg
• 0fc96cfb09d6280ebb435fc4bc71b89ba091dabc26e9325c6a13c1426e2d06ff NUnit.ConsoleRunner.NetCore.3.14.0.nupkg
• 90764fea3c43af10778560f389d4b87f04f480cd98505510db24f843c8e96963 nunit-console-runner.3.14.0.nupkg
• c94c4469cfbb78d4812285efb6d6c174bea7ed7082ef1ebf12ee6c9812c07eb9 NUnit.Console-3.14.0.msi
• e0a4c450e69f2554080b7438e89c04d1e8ef13f7d23b493376b270a9ed293c1a NUnit.Console-3.14.0.zip
• e5ed4d2ded6c415a4554b098920bf6d9429bac659d190aa2abaad3edd67ca53b NUnit.Engine.3.14.0.nupkg
• 9300659891f1b0cc32ef30b65d84642b37c6bb59dd37da4ad7e2c88f64b6318c NUnit.Engine.Api.3.14.0.nupkg

NUnit Console and Engine 3.13.2

As part of this release we had 3 issues closed.

This is another build-only milestone. The previous release, 3.13.1, required some intervention in order to complete correctly. The build fixes in this one are intended to allow publishing and release to run to completion.

There are no user-facing fixes or improvements in this release.

Build

• #1077 Don't push non-chocolatey packages to chocolatey!
• #1078 Don't publish -pre builds to MyGet
• #1080 Add --nopush option to the build

Choosing a Package

The package nunit-console-runner.nupkg is a Chocolatey package and should be installed using choco.exe. It is also available at chocolatey.org. All other .nupkg packages are intended for use with nuget.exe and may be downloaded from nuget.org as well as here.

SHA256 Hashes of the release artifacts

• 2e3e943b0d0820fd1667b1fed0f80d7c42cb2b058256d2c733214725418aff51 NUnit.Console.3.13.2.nupkg
• 0f1ac459d67484cb29ebbc6f485d6149fe17a032c8c637a59459f159657b9ea2 NUnit.ConsoleRunner.3.13.2.nupkg
• cf0cd7b61462a5a2efaf8e4a197da26eec790096bcd771a8efbf038a7a4a715d NUnit.ConsoleRunner.NetCore.3.13.2.nupkg
• a72378ebb7a937badcd531cdcb6ac66515222afd1c6546a75fbd7243785d0c06 nunit-console-runner.3.13.2.nupkg
• 91732f22a96d0abf43085524336150500921d57a4ecbb649409407be0e6e284d NUnit.Console-3.13.2.msi
• 17f28acc9ad14e1aa96a2f9d28642ebf2a0efed3bd2edebc09ef6e66990bdd27 NUnit.Console-3.13.2.zip
• 5b1b3e5da16f8708cca71d7c733e57e6ecc57e0db93ec68d64f4d78a3202d3a6 NUnit.Engine.3.13.2.nupkg
• 5e9d0715cedde1bac66e4520df0371fd622e4673c3b880288c298275001dbb51 NUnit.Engine.Api.3.13.2.nupkg

NUnit Console and Engine 3.13.1

As part of this release we had 9 issues closed.

This release is entirely made up of improvements to the build process and is being released in order to test that process. There are no user-facing bug fixes or improvements in this release as compared to 3.13.0.

Build

• #1029 Use newer cake version to avoid special handling of -SymbolPackageFormat snupkg
• #1047 Upgrade Cake to version 1.3
• #1059 Upgrade Cake to 2.0.0 and use Cake.Tool so we can build on all platforms
• #1061 Use GitVersion to determine package version to be produced
• #1062 Let PackageDefinition build the package itself
• #1064 Publish dev builds to MyGet using the Cake script
• #1065 Publish to chocolatey and nuget automatically for production releases.
• #1070 Automatically generate the release notes for a draft release on GitHub using GitReleaseManager.
• #1072 Automatically upload assets and perform the release on GitHub using GitReleaseManager.

Choosing a Package

The package nunit-console-runner.nupkg is a Chocolatey package and should be installed using choco.exe. It is also available at chocolatey.org. All other .nupkg packages are intended for use with nuget.exe and may be downloaded from nuget.org as well as here.

SHA256 Hashes of the release artifacts

• 131a2bb701102b5bf1066793e0c53f6c144c060ec248adf7c21cc64ba4873651 NUnit.Console.3.13.1.nupkg
• 758a3baa897ba4ef0da8394bf2aff7d2e21e1fe5a64e4a45aaafa8efd32e1977 NUnit.ConsoleRunner.3.13.1.nupkg
• 7f43b98d0f4562bb76e7de3b9ad515a1280d34145d40fd6353cd8b6d61e55842 NUnit.ConsoleRunner.NetCore.3.13.1.nupkg
• 83228f80ad0bd5634ac1c421ed6298ebc3fc36fd603783d51443a6f656ea8536 nunit-console-runner.3.13.1.nupkg
• ed0b7b1649f103d8160612710afde9e501808a87fe406337d43fc43eabe0228a NUnit.Console-3.13.1.msi
• 998181279a3a00d591cac81865a8601c836d624725e7a47cadb519ab40e29860 NUnit.Console-3.13.1.zip
• a62798ed943396694aab1f394bda3bef2aa3af12515882b407b221c4a75036ba NUnit.Engine.3.13.1.nupkg
• 717cac50c2a0ba1b782a82b26da7fbe3d0af121533117d610770a726066d37f9 NUnit.Engine.Api.3.13.1.nupkg

NUnit Console and Engine 3.13

This is the first release of the NUnit Console Runner, which allows running of both .NET Framework and .NET Core tests, either separately or in combination. The Console 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 is the availability of preemptive cancellation when the normal approach of requesting the test run to terminate itself doesn't work. This is an engine feature, available to any runners supporting cancellation.

See the Release Notes for a full list of changes.

Note: Packages will be available on nuget.org and chocolatey.org shortly. Release notes are in process.

.NET Core NUnit Console 3.12.0-beta2

This Beta release of the .NET Core NUnit console contains some fixes to extension loading, and the ability to use the runner as a .NET Core Tool. The .NET Core Console remains in Beta due to some unresolved dependency loading and framework targeting issues - contributions to fix these issues would be welcomed.

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.

See the Release Notes for a full list of changes.

NUnit Console and Engine 3.12

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.

See the Release Notes for a full list of changes.

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.