Fluent Assertions for xUnit

[PerthCharern]

I am a big fan of the Fluent Assertions framework http://fluentassertions.com/, which integrates well with xUnit.

It gets rid of the Assert.XXX syntax and use a more human-readable actual.Should().Be().EqualTo(expected) syntax. It also provides out-of-the-box support for deep object comparison. The error message pinpoints where exactly two objects are different.

I don't see a downside except from an extra dependency. This project is available on NuGet and widely used though, so I don't think that's too big of an issue either.

[darrelmiller]

Personally I can't stand using that style of interface, but as far as I am concerned, use what works for you.

[PerthCharern]

Oh okay. I am fine with the current way of doing it as well. The only main "feature" we will be missing is the object equivalency.

For unit tests that compare two objects, we don't have a good generic way to do so. Currently we would need to either serialize them, or implement their Equality manually.

[PerthCharern]

Not fully resolved yet. Will keep this open until we have migrated all tests.

[PerthCharern]

Fixed in #83

[PerthCharern]

My bad. I was using the wrong Find string. We still have Asserts in our code, so I'll leave this open and fix.