Release Notes: January 20, 2015

xUnit.net v2 2.0 RC 1

Core framework

Added support for 64-bit iOS Universal via Xamarin.
Added configuration file support. For more information, see Configuring xUnit.net.
Updated ASP.NET 5 support to use ASP.NET 5 Beta 2. For more information, see Getting started with xUnit.net and ASP.NET 5.
Added nullable boolean versions of Assert.True and Assert.False.
Removed Assert.None, since it was a duplicate of Assert.DoesNotContain.
Improved error reporting when accidentally using [InlineData] with [Fact].
Displaying parameter values for theories will now use ToString, if your data object overrides it (this mimics the behavior in xUnit.net v1). If your data object does not override ToString, then the parameter value will continue to use the new JSON-like display.
Unit test code that uses the Task Parallel library will no longer share the task scheduler used by xUnit.net (which is how the test framework limits parallelism). This has the effect that your unit tests can create any number of tasks and run in massively parallel scenarios without being constrained by xUnit.net's limitations for tests running in parallel. This should also make it much harder to deadlock unit tests using the TPL.
BUG: Test output was missing from the XML output.
BUG: Test output was missing from the HTML output.
BUG: Test timing shouldn't have been rounded in the XML output.
BUG: There was an issue with project and solution being in the same folder.
BUG: Fixture disposal errors were not consistently reported to runners.
BUG: Evidence was missing from the remote app domain, causing periodic deserialization failures.

Extensibility

Added ConfigReader to get the configuration for a test assembly.
Introduced IDiagnosticMessage to report diagnotics from the framework to the runner.
Made AsyncTestSyncContext public.
Made TestInvoker>T<.CreateTestClass virtual.
Added XunitTestRunner.InvokeTestMethodAsync as a virtual method.
Exposed XunitTestRunner.BeforeAfterAttributes to inheritors.
Removed XunitDiscoveryOptions and XunitExecutionOptions. They were replaced with static factories on TestFrameworkOptions instead. In addition, interfaces are used to tag discovery vs. execution options, and extension methods were introduced that allow runner authors to manipulate them separately.
Added the ability to enable synchronous message delivery during test discovery (this was already an option during test execution). Set this using
An issue was found with serialization failures of test cases inside the Visual Studio runner that caused it to spin forever when developers returned non-serializable test cases. This usually only surfaces when running tests inside Visual Studio, since this is the only runner that serializes test cases. For examples of how to correctly serialize a test case, please see RetryTestCase in the RetryFactExample sample.

This release has given unique names to the execution and runner utility DLLs, in an effort to fix issues related to device-based unit tests need access to both desktop DLLs (for discovery inside Visual Studio) as well as the device specific runners. These DLLs are paired up based on platform:

Desktop CLR / PCLs	`xunit.execution.desktop.dll` `xunit.runner.utility.desktop.dll`
Modern Windows 8	`xunit.execution.win8.dll` `xunit.runner.utility.win8.dll`
Windows Phone 8 (Silverlight)	`xunit.execution.wp8.dll` `xunit.runner.utility.wp8.dll`
Universal Apps (Win81/WPA81)	`xunit.execution.universal.dll` `xunit.runner.utility.universal.dll`
Xamarin (MonoAndroid)	`xunit.execution.MonoAndroid.dll` `xunit.runner.utility.MonoAndroid.dll`
Xamarin (MonoTouch)	`xunit.execution.MonoTouch.dll` `xunit.runner.utility.MonoTouch.dll`
Xamarin (iOS Universal)	`xunit.execution.iOS-Universal.dll` `xunit.runner.utility.iOS-Universal.dll`

There is a single NuGet package for execution and runners, which includes DLLs for all platforms (xunit.extensibility.execution and xunit.runner.utility).

Console, MSBuild, and TestDriven.NET Runners

Added support for configuration files. For more information, see Configuring xUnit.net.

ASP.NET 5 Runner 2.0 RC1

For information on using xUnit.net from within ASP.NET 5, see Getting started with xUnit.net and ASP.NET 5.

Updated to ASP.NET v5 Beta 2.

Visual Studio Runner 2.0 RC1

For information on using xUnit.net from within Visual Studio, see Running xUnit.net tests in Visual Studio.

Note: This release supports all released versions of xUnit.net v1, as well as v2 2.0 RC1 or later. It does not support any earlier versions of xUnit.net v2.

Added support for configuration files. For more information, see Configuring xUnit.net.
An issue was found with serialization failures of test cases inside the Visual Studio runner that caused it to spin forever when developers returned non-serializable test cases. This usually only surfaces when running tests inside Visual Studio, since this is the only runner that serializes test cases. For examples of how to correctly serialize a test case, please see RetryTestCase in the RetryFactExample sample.
The three Visual Studio runner NuGet packages have been collapsed down into just a single package: xunit.runner.visualstudio. When upgrading packages, please remove the old device-specific NuGet packages (win8 and wpa81) and install the single package instead.
BUG: Collection definitions were not working the Visual Studio runner.