nunit

This release of NUnit expands on parallel test execution to allow test methods to be run in parallel. Please see the Parallelizable Attribute for more information.

NUnit 3.7 also drops the Portable build of the framework and replaces it with a .NET Standard 1.3 version to complement the .NET Standard 1.6 version. This change enables several constraints and other features in the .NET Standard builds that weren't available in portable like Path and Directory based asserts.

The AssertionHelper class has been deprecated because it is seldom used and has not received any of the updates that Asserts and Constraints receive. If your code is using the AssertionHelper class, we recommend that you migrate your asserts.

This is a hotfix release of the framework that addresses critical issues found in the 3.6 release.

Issues Resolved

• 1962 A Theory with no data passes
• 1986 NUnitLite ignores --workers option
• 1994 NUnitLite runner crashing when --trace is specified
• 2017 Two NUnit project's tests fail on systems with comma decimal mark settings
• 2043 Regression in 3.6.0 when catching AssertionException

This release of the framework no longer includes builds for Compact Framework or for SilverLight, but adds a .NET Standard 1.6 build. If anyone still using Compact Framework or SilverLight and would like to continue development on those versions of the framework, please contact the NUnit team.

Framework

• .NET Standard 1.6 is now supported
• Adds support for Multiple Assert blocks
• Added the --params option to NUnitLite
• Theories now support Nullable enums
• Improved assert error messages to help differentiate differences in values
• Added warnings with Warn.If(), Warn.Unless() and Assert.Warn()
• Enabled Path, File and Directory Asserts/Contraints for .NET Core testing
• Added NonTestAssemblyAttribute for use by third-party developers to indicate that their assemblies reference the NUnit framework, but do not contain tests

See the release notes for a complete list of changes.

This is the first version of NUnit where the framework will be released separately from the
console runner, engine and other extensions. From this point forward, the NUnit Framework will be
released on its own schedule that is not bound to that of any other NUnit project and version numbers
may diverge over time.

This is also the first release where the NUnit Framework will not be included in the installer. Only
the console runner, engine and extensions will be available as an MSI installer. We recommend that you
use the NUnit NuGet packages for the framework, but a ZIP file with the binaries will also be available.

Framework

• Added Assert.Zero and Assert.NotZero methods
• Tests with a Timeout will no longer timeout while you are debugging

See the release notes for a complete list of changes.

Console Runner

• A new option, --list-extensions, will display all the engine extensions that
  have been installed by the engine.

Issues Resolved

• 1623 NUnit 3.4 is not integrated with TeamCity
• 1626 NUnit.ConsoleRunner is not picking up NUnit.Extension.NUnitV2ResultWriter
• 1628 Agent's process stays in memory when it was failed to unload AppDomain
• 1635 Console option to list loaded extensions

Framework

• Improvements in comparing equality using IEquatable
• Test case names will only be truncated if the runner requests it or it is overridden on the command line
  with the --test-name-format option
• The .NET 2.0 version of the framework now includes LINQ. If your tests target .NET 2.0, you can now use
  LINQ queries in your tests

Engine

• The TeamCity event listener has been separated out into an engine extension
• Fixed numerous issues around thread safety of parallel test runs
• Additional fixes to reduce memory usage
• Fixes for Mono 4.4

Console Runner

• There is a new --params command line option that allows you to pass parameters to your tests
  which can be retrieved using TestContext.Parameters
• Another new command line option --loaduserprofile causes the User Profile to be loaded into the
  NUnit Agent process.

See the release notes for a complete list of changes.

This is mainly a bugfix release, but it contains several features that were intended for the 3.4 release.

NUnit 3.2 introduced a change that ran each test on its own thread. In hindsight, this was a mistake and made it difficult for tests that required a specific context. We have reverted to the previous behaviour of running tests on the same thread unless a test attribute requires a new thread. We also added a new [SingleThreaded] attribute that you can apply to your test fixture to explicitly declare the requirement. Using this attribute allows the framework to raise an error if you mistakenly use an attribute on a test that requires a new thread.

Developers who target .NET 3.5 using the .NET 2.0 version of the framework ran into conflicts with some of the compatibility classes in NUnit. To fix this, we have reinstated the .NET 3.5 version of NUnit.

Very large test suites were using a large amount of memory causing paging and slow test runs on some systems. To reduce memory pressure, we are now releasing objects earlier, greatly reducing memory requirements.

The NUnit Engine now has an EventListener extension point for people who want to write extensions that respond to specific events during test runs.

For a full list of issues fixed in this release, please see the release notes.

In addition to numerous bug fixes, this release adds the long requested OrderAttribute, a new Assert.ThrowsAsync, Assert.That(0, Is.Zero) and other enhancements.

For a full list of issues fixed in this release, please see the release notes.

This release fixes critical issues reported against the initial 3.0 release, mainly around compatibility producing the NUnit 2 XML output format and async support for Windows 10. For a full list of issues fixed in this release, please see the release notes.

This is the final release of NUnit 3.0. See the release notes for details of all its features.

This release fixes some errors in RC2 and is expected to be the final RC.

This is the second release candidate for NUnit 3.0 which fixes a few issues that were found in the initial release. All the features we intend to include are present and this is the final step before releasing. If we have to make changes due to errors there will be additional release candidates. Otherwise, this build will be re-packaged as the final release.

For details of changes in this release, see the release notes.

This is the initial release candidate for NUnit 3.0. All the features we intend to include are present and this is the final step before releasing. If we have to make changes due to errors there will be additional release candidates. Otherwise, this build will be re-packaged as the final release.

For details of changes in this release, see the release notes at https://github.com/nunit/docs/wiki/Release-Notes

This is the fifth beta release of NUnit 3.0. We had a number of new features added and decided to have an additional beta before the final release.

For changes to the beta-5 release as well as cumulative changes see the release notes at https://github.com/nunit/docs/wiki/Release-Notes

This is the fourth beta release of NUnit 3.0. We hope this will be the last beta before the final release, but will make the decision after reviewing the outstanding issues.

For changes to the beta-4 release as well as cumulative changes see the release notes at https://github.com/nunit/nunit/wiki/Release-Notes

This is the third beta release of NUnit 3.0. We are planning one more beta next month before the final release.

This release changes the Engine API, so if you have a previous 3.0 release installed, you must uninstall it before installing this release.

For changes to the beta-3 release as well as cumulative changes see the release notes at https://github.com/nunit/nunit/wiki/Release-Notes

This is the second beta release of NUnit 3.0 bringing us one step closer to the final release. This release splits the distribution of the Compact Framework version of the NUnit Framework out of the main package and adds a new core engine for use by devices and similar situations where reduced functionality is compensated for by reduced size and simplicity of usage.

For changes to the beta-2 release as well as cumulative changes see the release notes at https://github.com/nunit/nunit/wiki/Release-Notes

This is the first beta release of NUnit 3.0.

For changes to the beta-2 release as well as cumulative changes see the release notes at https://github.com/nunit/nunit/wiki/Release-Notes

This is the fifth (and probably last) Alpha release of NUnit 3.0. It adds some important features, including implementation of addins in the test engine and provision of Windows installers for the framework and console runner.

This latest Alpha release of NUnit 3.0 adds several new features, including a driver that allows the 3.0 Test Engine to run tests created under NUnit 2.x and support for both NUnit and Visual Studio project formats.