Release Notes: October 5, 2016

Since the last release, we have moved to The .NET Foundation. The most visible sign of this is that you'll see the foundation CLA bot monitoring our pull requests. We are also operating under their Code of Conduct. Thank you to the .NET Foundation for our new home!

xUnit.net v2 2.2 Beta 3

Core framework

Test discovery and execution performance has been dramatically improved when app domains are being used (the default behavior). This performance improvement requires runner changes; the shipped runners (Console, MSBuild, TestDriven.Net, and Visual Studio) have all been updated.
Support for detecting hung unit tests has been added. It is a configuration option which can be enabled in your configuration file.
Support for F# async tests was added. For an example of how to write an F# async test, please see our acceptance test for this feature.
Performance of the AppVeyor runner reporter was improved.
BUG: Fixed an issue where async fixtures could end up being initialized multiple times.
BUG: The automatic environmental support for the AppVeyor and TeamCity runner reporters was incorrectly triggering if the environment variable was present (but empty).

Assertion library

Added support for using NuGet v3 to pull in Assert as source.
xunit.assert.source is now correctly marked as a development-time dependency in the NuGet package.

Console runner

A new -noautoreporters switch was added to disable any automatic environmentally enabled runner reporters (for example, AppVeyor or TeamCity).

MSBuild runner

A new NoAutoReporters property was added to disable any automatic environmentally enabled runner reporters (for example, AppVeyor or TeamCity).
The deprecation properties TeamCity and Verbose were officially removed. The Reporter property (with a value of teamcity or verbose) should be used instead.

Extensibility

A new interface IMessageSinkWithTypes was added as part of the work to dramatically improve the discovery and execution performance of v2 unit tests. Runners which have custom message sinks should implement this new interface rather than the older IMessageSink interface. Most of the methods in the system have been updated (or extended) to accept both interface types. When that wasn't possible, two classes were added that can wrap implementations of one into the other (for more information, see MessageSinkAdapter.Wrap and MessageSinkWithTypesAdapter.Wrap).
The visitor classes (based on IMessageSink) have been deprecated due to their poor performance. New event-based sink classes (based on IMessageSinkWithTypes) have replaced them. The new sink classes use events that can be subscribed to; these replace the old virtual methods in the visitor classes. The new sink classes have a significantly improved class hiearchy.
Runner reporter authors should return message hanlders that implement both IMessageSink and IMessageSinkWithTypes for best compatibility and performance. The DefaultRunnerReporter and DefaultRunnerReporterMessageHandler base classes has been deprecated, and replaced with DefaultRunnerReporterWithTypes and DefaultRunnerReporterWithTypesMessageHandler, which implement the new high-performance message sink interface.
TestDiscoverySink now includes the ability to cancel test discovery; TestDiscoveryVisitor did not include this ability.
BUG: Fixed an issue with null refs happening in TestRunner.cs.

Visual Studio Runner 2.2 Beta 3

For information on using xUnit.net from within Visual Studio, see Running tests with Visual Studio in the Getting Started documentation.

BUG: Fixed an issue with unit test DLL paths that surfaced when using vstest.console.exe.
BUG: Fixed an issue with source information for referenced assemblies (other than the assembly under test), which would manifest as misisng source information for test base classes in other assemblies.