Releases: fluentassertions/fluentassertions
Releases · fluentassertions/fluentassertions
5.5.3
5.5.2
5.5.1
- {New} Now provides a hint when strings differ in length and contain differences - #915, #907
- {New} Added
ThrowAsync
,ThrowExactlyAsync
andNotThrowAsync
- #931 - {New} Added support for
Should().Throw
andShould().NotThrow
forFunc<T>
- #951 - {New} Added support for
private protected
access modifier - #932 - {New} Updated
BeApproximately
to support nullable types for both the subject and the expectation nullable - #934 - {New} Added
async
version ofExecutionTime
to - #938 - {New} Updated
NotBeApproximately
to accepting nullable subject and expectation - #939 - {New}
type.Should().Be(type)
now support open generics - #954, #955 - {Fix} Minor performance improvements to prevent rendering messages if a test did not fail - #921, #915
- {Fix} Improve performance of
Should().AllBeEquivalentTo()
- #920, #914 - {Fix} Improve the presentation of enums to include the value and the number - #923, #897
- {Fix}
BeEquivalentTo
withWithStrictOrdering
produced messy failure message - #918 - {Fix} Fixes detecting checking equivalency of a
null
subject to a dictionary - #933 - {Fix} Fixes duplicate conversions being mentioned in the output of the equivalency API - #941
- {Fix} Comparing an object graph against
IEnumerable
now works now as expected - #911 - {Fix} Selecting members during object graph assertions now better handles
new
overrides -#960, #956
Note In versions prior to 5.5, FA may have skipped certain properties in the equivalency comparison. #960 fixes this, so this may cause some breaking changes.
Lots of kudos @jnyrup and @krajek for a majority for the work in this release.
5.5.0
- {Breaking Change} Since the addition of
Should().Throw
andShould().NotThrow
forFunc<T>
, assertionsShould().Be
andShould().NotBe
can't be used onFunc<T>
objects anymore, so this may cause breaking changes. These instances can easily be replaced withShould().BeSameAs
andShould().NotBeSameAs
as these types are compared by references.
5.4.2
- {Fix} Limits the depth of rendering an object to a max of 5 to prevent OOM exceptions - #898
- {Fix} Show the entire exception instead of just the message when an
async
function throws - #892 - {Fix} Fixed a StackOverflow while comparing an self-returning enumerable - #887
- {Fix} Custom rules (
Using().WhenTypeIs()
) were not executed on dictionary equivalency assertions - #886 - {Fix} The failure message of
HaveOffset
returned the seconds instead of the offset - #883
5.4.1
5.4.0
5.3.2
- {Fix}
AssertionScope
did not work withGenericCollectionAssertions
- #835 - {Fix} Improved the performance of asserting large arrays for equivalency - #840
- {Fix} Handle an edge case that only seems to happen under NCrunch - #841
- {Fix} Resolved potential deadlocks and long-running threads in the execution time assertions - #842
Kudos to @peterekepeter and @jnyrup for those fixes.
5.3.0
- {Fix} Fix String.ContainAll param documentation - #810
- {Fix} Test framework detection didn't always work under .NET Core 2.0 - #825
- {New}
MethodImplAttribute
now works with(Not)BeDecoratedWith
- #804 - {New} Added support for integral types to
[Not]BeCloseTo
- #803 - {New} Increased the accuracy of
[Not]BeCloseTo
forDateTime[Offset]
toTick
precision instead of milliseconds - #820 - {New} Many performance improvements to
BeEquivalentTo
- #817
Kudos to @jnyrup for making this release possible. Thanks to @melchiork for contributing #825.
5.2.0
- {New} Downgraded to .NET Standard 1.3 - #780
- {New} Added support for
(Not)Be(Abstract|Sealed|Static)
class assertions implemented - #796 - {Fix} More null checks for
NumericAssertions
- #788 - {Fix} Nullable properties of type
IEnumerable
should still be treated as enumerables - #793 - {Fix} Improved the failure messages for
(Not)BeApproximately
- #795 - {Fix} Bumped dependency on
System.ValueTuple
to 4.4. - #802