Fluent assertions release 1.2.2

The last few days I’ve been working on a new release of the Fluent Assertions, since I’ve started using them again on my current project. I ran into a bug myself and saw a few bugs and feature requests on the issue tracker, so I decided to fix some of them.

I just released version 1.2.2 so you can download it here.

The following fixes / new features are available:

• Issue 8463 – Comparing strings with trailing whitespace can have a more detailed error message
  The error message now indicates that one of the strings has trailing spaces. This has also been changed in the BeEquivalentTo.
• Issue 8710 – CollectionAssertions.NotBeEmpty should properly detect <null>
  All collection assertions are now protected against a null collection. You no longer get an ArgumentNullException when this occurs, but a decent error message stating that <null> was found.
• Issue 8726 – string.Should().Be(“”) should detect <null>
  Now protected against a <null> string. Also gives a decent error message instead of an ArgumentNullException.
• Issue 8842 – GenericCollectionAsserts methods should properly detect <null>
  These assertions have also been protected to a <null> as subject.
• Issue 8843 – IndexOutOfRangeException when ShouldThrow with specific message
  This was a very specific error which I encountered when the subject string is exactly the start of the expected string. This gives a decent error now instead of an IndexOutOfRangeException.
• Support for string.Should().BeNullOrEmpty() and string.Should().NotBeNullOrEmpty.
• Fixed a bug in collection.Should().ContainInOrder() when the sequence contains duplicate items.

Hope these fixes will also be helpful to you all. Download the latest release now and let us know if you have any suggestions of bugs found.