It’s only a few days ago since we released the first version of Fluent Assertions, and we already have a new release. The reason for this is that the first release was just the public release of an internal set of classes that we’ve been using for a year or so. But this week, we've worked hard to add some important missing features that we really needed, and also improve resilience against illegal arguments such as an empty collection or null. Release 1.1 includes the following improvements.
- All dependencies on MSTest assemblies have been removed. So assertions will work with all testing frameworks.
- Added support for Silverlight
- Improved the verification messages around assertion of collections so that you don't need any debugging to figure out what went wrong.
- Added object.Should().BeAssignableTo()
- Added object.Should().Satisfy() to verify against a lambda or delegate.
- Added extension methods on an Action or Action<T> which allows better support for the AAA syntax. We've rewritten a large portion of the framework's unit tests and it definitely improves unit test maintenance.
- Added a ValueOf property to the exception assertions syntax that allows chaining additional Should()s on the properties of the exception.