Release Notes: April 6, 2017

xUnit.net 2.3 Beta 1

Assert.Empty will now include the collection in the error message when the assert fails.
Added support for IComparable<> in Assert.Equal.
Improved compatibility with IEquatable<> and Assert.Equal.

The console runner has been ported to support .NET Core, through a new dotnet xunit command line tool. For more information on using the new .NET Core SDK console runner, see Getting Started with xUnit.net (.NET Core / ASP.NET Core).
When importing the xunit.runner.console NuGet package, you now have access to two properties which point to the on-disk location of the console runner executable: XunitConsolePath points to xunit.console.exe, and XunitConsolePathX86 points to xunit.console.x86.exe.

Added a netcoreapp1.0 version of xunit.runner.utility and xunit.runner.reporters.
Started the process of separating user diagnostic messages from internal diagnostic messages. Runners have new options (as do configuration files) for enabling one vs. the other. This should make debugging extensibility projects simpler. This work is ongoing, so if you see internal diagnostic messages showing up without the switch, please feel free to file an issue.

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

We've incorporated more performance improvements, especially when testing desktop CLR projects.
Skipped messages now show the skip reason in the output of the test. Previously, the skip message was not available.
BUG: Fixed an issue introduced in 2.2 RTM which caused CodeLens to stop working for [Fact] tests.