Today, we're shipping three new releases:
It's been 3 weeks since the release of 2.6.2 RTM.
As always, we'd like to thank all the users who contributed to the success of xUnit.net through usage, feedback, and code. 🎉
These release notes are a comprehensive list of changes from 2.6.2 to 2.6.3.
Assert.Equal
and Assert.NotEqual
)
with the overload that takes a comparison function, while comparing two sets (that is, any
collection implementing ISet<T>
or IReadOnlySet<T>
) will
now throw. Previously the behavior was undefined. The reasoning behind this inspired a new
documentation page ("Equality with hash sets vs.
linear containers"), which describes the reasoning behind this change.
IEquatable<T>
higher than attempting to treat items as containers.
This allows developers who want to customize container comparison to implement
this interface. Note that all other comparison interfaces remain lower priority,
so this is the only supported interface for customized container comparison.
xunit/xunit#2828
Assert.Contains
and Assert.DoesNotContain
for
SortedSet<T>
and ImmutableSortedSet<T>
have been
added, to help deal with compiler ambiguity.
xunit/xunit#2811
null
values in dictionaries weren't
being properly compared.
xunit/xunit#2824
ExecutionSink
)
which performs all the duties of the previously separate classes. These classes already had
strong ordering dependencies on one another, and the current implementation of those classes
were causing an issue where sometimes XML output was missing, due to a race condition. For
an example of the changes to use the new class, please see
this
commit which updates the Visual Studio adapter to use the new class.
xunit/xunit#2090