Release Notes: October 19, 2017
xUnit.net 2.3.1 RC 1
Removed external dependencies. This primarily caused issues with developers who wanted to use a newer
version of JSON.NET than we were linked against (9.0.1), but also affected uses of
dotnet xunit runner
- Optimized assembly resolution lookup performance.
BUG: Assembly resolution sometimes failed on case-sensitive file systems (this
primarily affected Linux users, as Windows and OS X by default use case-preserving but
case-insensitive file systems).
BUG: Unmanaged library lookup would sometimes fail because of names which didn't
match the filename (for example, asking for 'foo' but the library is really 'libfoo'). This primarily
affected Linux and OS X users where dynamic libraries tend to have prefixes like 'lib'.
BUG: Fixed an issue where the XML results file was being over-written without
erasing the old contents, the end result of which could be corrupted XML files.
BUG: Fixed an issue where MSBuild runner reporters were not working. This was
most obviously affecting TeamCity and AppVeyor users who lost their test reporting.
BUG: The XML results output file was being left open longer than intended. Now
it should be closed by the time the
<xunit> task has completed.
Visual Studio runner
For information on using xUnit.net from within Visual Studio, see
tests with Visual Studio in the Getting Started documentation.
BUG: Fixed issues with the performance-optimized serialization that were
[Fact] tests to be broken with Live Unit Testing.
BUG: Fixed an issue where test classes with mixed facts and theories
and class/collection fixtures ended up with two fixtures being created (one for the
facts and one for the theories).
BUG: Fixed an issue where sometimes source file mappings were broken,
especially with projects whose name started with 'n'. (Yes, really.)