Release Notes: May 3, 2015
xUnit.net v2 2.1 Beta 2
Core framework
- Added support for DNX Beta 4 (including ASP.NET 5 Beta 4).
- Display of generics in theory test names was dramatically improved.
- Added support for unsigned types in serialization.
- Added test case output support for TeamCity.
-
BUG: xUnit.net v1 support was inconsistent about
sending ClassFinished and CollectionFinished messages.
-
BUG: Fixed an issue where arrays of types other than
object were causing serialization issues.
-
BUG: Fixed an issue with XML output where illegal
characters were trying to be written.
-
BUG: Fixed an issue with Mono where some ASP.NET v5
tests would lose access to ambient runtime values.
-
BUG: Fixed an issue with Xamarin device runner projects
where
xunit.execution.{platform}
was not being linked into
the project.
Console Runner
-
BUG: Fixed an issue where some exceptions without stack
traces were causing runner failures.
Visual Studio Runner 2.1 Beta 2
For information on using xUnit.net from within Visual Studio, see
Running xUnit.net tests in Visual
Studio.
-
BUG: Test discovery failures were being reported with error
messages, which caused Team Build to report projects with mixed .NET and
C/C++ projects to be "Partially Successful", even though all appropriate
unit tests passed.
-
BUG: Diagnostic message output was missing the xUnit.net
banner and execution time.
DNX Runner 2.1 Beta 2
The ASP.NET runner has been renamed to the DNX runner, and is now capable of running
unit tests for all DNX-based projects (not just ASP.NET v5). The runner package has
been renamed (xunit.runner.aspnet
=> xunit.runner.dnx
) as
has the GitHub project (now at
https://github.com/xunit/dnx.xunit).
- Added support for DNX Beta 4 (including ASP.NET 5 Beta 4).
- Support for running tests in Visual Studio requires VS 2015 RC or later.
-
Source line mappings are now available in Visual Studio when running DNX
tests, which means you can click on test method names in Test Explorer to jump
directly to the unit test now.