Assert.None, since it was a duplicate of
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.
ConfigReader to get the configuration for a test assembly.
IDiagnosticMessage to report diagnotics from the framework to the runner.
XunitTestRunner.InvokeTestMethodAsync as a virtual method.
XunitTestRunner.BeforeAfterAttributes to inheritors.
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.
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
|Modern Windows 8
|Windows Phone 8 (Silverlight)
|Universal Apps (Win81/WPA81)
|Xamarin (iOS Universal)
There is a single NuGet package for execution and runners, which includes DLLs for all
For information on using xUnit.net from within ASP.NET 5, see Getting started with xUnit.net and ASP.NET 5.
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.
xunit.runner.visualstudio. When upgrading packages, please remove
the old device-specific NuGet packages (
install the single package instead.