Release Notes: February 17, 2015

xUnit.net v2 2.0 RC 2

Core framework

BUG: Times in the XML report weren't written in the invariant culture.

Extensibility

Removed all dependencies on .NET serialization, instead standardizing on the IXunitSerializable interface. This means anybody implementing serialization for test cases no longer has to implement it twice, and can now remove the [Serialization] constructor and remove the implementation of ISerializable. The new serialization system supports most of the built-in intrinsic types (int, long, float, double, decimal, string, and their nullable counterparts), any type which implements IXunitSerializable, and arrays which contain supported serializable types. (Note: the old interface IGetTypeData is no longer supported. Extenders should implement IXunitSerializable instead.)
We added an instance of IMessageSink that is used solely for receiving diagnostic messages. Runners can optionally pass this when they create either XunitFrontController or Xunit2, and it is propagated throughout the system. All extensibility points (implementations of IDataDiscoverer, ITestCaseOrderer, ITestCollectionOrderer, ITestFrameworkTypeDiscoverer, ITraitDiscoverer, IXunitTestCaseDiscoverer, IXunitTestCollectionFactory, ITestFramework, ITestFrameworkDiscoverer, and ITestFrameworkExecutor) can now get access to this message sink by adding IMessageSink as a constructor parameter.
We removed EnvironmentalWarning and IMessageAggregator. Anything which had previously been reporting environmental warnings during discovery has now been converted to use the diagnostic message sink described above. In addition, several code locations that previously could not log issues (because they happened outside of discovery or execution) are now able to report diagnostic messages. This should aid developers writing extensibility points because we can now report more issues related to creating and using these extensions. (We also updated IDiscoveryCompleteMessage to remove the Warnings property.)
Exposed XunitTestInvoker.BeforeAfterAttributes to inheritors.
BUG: Fixed an issue where assembly-level test collection and parallelization configuration options were being ignored.

Console Runner

Added a -nologo switch to suppress the runner header/copyright.
Added a -quiet switch to suppress discovery/execution meta-messages.
Added a -debug switch to launch the debugger on startup.
Diagnostic messages are now being reported to the console as warnings.
Diagnostic messages are turned off by default. To enable diagnostic messages for a given assembly, please see Configuring xUnit.net.
Skips are written to STDOUT instead of STDERR, as some build systems which monitor STDERR to fail a build (which was causing them to fail when skipped tests were present).
BUG: TeamCity v9 was seemingly incorrectly reporting the number of tests, because it was combining similar tests together and treating them as multiple invocations of the same test.

MSBuild Runner

Diagnostic messages are now being reported to MSBuild as warnings.
Diagnostic messages are turned off by default. To enable diagnostic messages for a given assembly, please see Configuring xUnit.net.
BUG: TeamCity v9 was seemingly incorrectly reporting the number of tests, because it was combining similar tests together and treating them as multiple invocations of the same test.

Visual Studio Runner 2.0 RC2

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 RC2 or later. It does not support any earlier versions of xUnit.net v2.

Diagnostic messages are now being reported to Visual Studio as warnings. You can see these messages in the Test pane of the Output window. Note: diagnostic messages are only supported during execution for desktop and PCL projects (they are not supported for Windows app tests or Windows Phone app tests). Diagnostic messages are supported during discovery for all platforms, since discovery always happens in the desktop CLR.
Diagnostic messages are turned off by default. To enable diagnostic messages for a given assembly, please see Configuring xUnit.net.
BUG: Runners for Windows 8/8.1 apps and Windows Phone 8.1 apps were inadvertantly broken (some tests would only run under some circumstances).
BUG: Fact methods with parameters were not showing the error correctly inside of the Visual Studio runner.

ASP.NET 5 Runner 2.0 RC2

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

Note: This release supports xUnit.net v2 2.0 RC2 or later. It does not support any earlier versions of xUnit.net v2.

Added a -nologo switch to suppress the runner header/copyright.
Added a -quiet switch to suppress discovery/execution meta-messages.
Added a -debug switch to launch the debugger on startup. Note that this only works with the desktop CLR, as Core CLR does not support Debugger.Launch().
The runner currently supports only console invocation. Support for running tests inside of Visual Studio will come in a later release, once the support in ASP.NET has stabilized.
BUG: The command line runner was not reporting enough information when assembly load failures happened (in particular, compilation errors were not being) reported.
BUG: The -? was being ignored.