Today, we're shipping xUnit.net 2.2. This includes 2.2 RTM builds of the core framework and the Visual Studio runner.
It has been approximately 17 months since we shipped 2.1. The delay of the final release of 2.2 had been pushed back to align roughly with the release of .NET Core 1.0. While that was released back in June of last year, the pieces we relied upon (namely, the .NET CLI SDK) have remained in pre-release; their RTM is just a couple weeks away with the shipping of Visual Studio 2017.
We have just begun work on a new runner for .NET Core which will supplant (and
dramatically improve) the command-line test runner experience when compared to
dotnet test. Beta releases of that runner will start shipping soon.
Once again, we'd like to thank all the users who contributed to the success of xUnit.net through usage, feedback, and code contributions. We had too many contributors this time around to thank individually, so know that every bug reported, every line of code PR'd, every conversation contributed to on Slack, were all appreciated!
Important note: If you are using Visual Studio 2013, you must use NuGet 2.12 or
later to use xUnit.net 2.2, because support for
required. You will not be able to use xUnit.net 2.2 with Visual Studio 2012
(if Visual Studio 2012 support is important, please stick with xUnit.net 2.1).
netstandard1.1, you will still be able to link your desktop unit test projects that target 4.5 and 4.5.1, but they will not show up in the Visual Studio runner, and they will not get desktop features like AppDomain isolation. Make sure you upgrade the .NET version of your projects before installing the new NuGet packages.)
dotnet test). Both the .NET CLI SDK and Visual Studio 2017 ship with templates for making xUnit.net projects. (Note: .NET Core support is limited to Visual Studio 2017--aka, MSBuild SDK-style projects. We have discontinued support for Visual Studio 2015--aka, project.json-style projects.)
Assert.Allto include the failing item when reporting assertion failures
Assert.Collectionto include the collection when reporting assertion failures
[,]no longer incorrectly show as equal
ISetimplementations which are either not generic, or have more generic parameters than just the item type
The following individual releases contributed to 2.2:
In addition, there were several RC builds that did not include release notes. The content of those releases have been rolled up into the text above.