Commented Issue: Add .NET 4.5 assembly [11836]
Add a .NET 4.5 assembly and a separate specs assembly for .NET4.5 as well.Comments: Associated with changeset 76686.
View ArticleCommented Issue: Exclude properties on nested objects [11841]
We'd like to compare two aggregate roots ignoring a few audit properties (CreatedBy, CreatedOn) on all entities within the root.AllPropertiesBut() only excludes properties on the root object.I think...
View ArticleSource code checked in, #76707
Removed the testrunsettings.config to fix the issue where VS11 wasn't loading all specs from all unit test projects. Removed the dedicated WinRT solution file. Added specific .NET versions of...
View ArticleCreated Issue: Support asserting that a datetime is close to another datetime...
It would be nice if you could assert that a DateTime value is close to another DateTime value. This can be useful for example when a database truncates datetime values. The acceptable difference in...
View ArticleCommented Issue: Exclude properties on nested objects [11841]
We'd like to compare two aggregate roots ignoring a few audit properties (CreatedBy, CreatedOn) on all entities within the root.AllPropertiesBut() only excludes properties on the root object.I think...
View ArticleCreated Issue: When comparing dates it doesn't display milliseconds [12072]
In the comparison the milliseconds are taken into account but when displaying an assertion is doesn't show them. This can lead to strange result see below.Expected <2012-04-25 20:40:18>, but...
View ArticleSource code checked in, #76792
Changed the formatting of datetime values, to include the milliseconds when they are relevant.
View ArticleCommented Issue: When comparing dates it doesn't display milliseconds [12072]
In the comparison the milliseconds are taken into account but when displaying an assertion is doesn't show them. This can lead to strange result see below.Expected <2012-04-25 20:40:18>, but...
View ArticleCommented Issue: Support asserting that a datetime is close to another...
It would be nice if you could assert that a DateTime value is close to another DateTime value. This can be useful for example when a database truncates datetime values. The acceptable difference in...
View ArticleCommented Issue: Exclude properties on nested objects [11841]
We'd like to compare two aggregate roots ignoring a few audit properties (CreatedBy, CreatedOn) on all entities within the root.AllPropertiesBut() only excludes properties on the root object.I think...
View ArticleCreated Issue: Add collections.Should().BeInOrder()/NotBeInOrder() [12103]
See http://fluentassertions.codeplex.com/discussions/352038
View ArticleNew Post: GenericCollectionAssertions BeInOrder/NotBeInOrder
Added as a change request for release 2.0.0.
View ArticleCommented Issue: Exclude properties on nested objects [11841]
We'd like to compare two aggregate roots ignoring a few audit properties (CreatedBy, CreatedOn) on all entities within the root.AllPropertiesBut() only excludes properties on the root object.I think...
View ArticleUpdated Wiki: Documentation
Supported Test Frameworks Fluent Assertions supports MSTest, NUnit, XUnit and MSpec. You can simply add a reference to the corresponding test framework assembly to the unit test project. Fluent...
View ArticleNew Post: FloatingPointExtensions Bug
Hello everyone That's the first time for me to start a discussion, therefore I hope I do everything correctly.. In our project we are using decimal? sometimes and I'd like to "re-use" the existing...
View ArticleNew Post: Best way to test for exception on class's Default Indexer Property
Given the following class: class MyClass { private List<string> myList; string this[int index] { return myList[index]; } } I can use it like this: string TestValue = myClass[5]; But how do I test...
View ArticleNew Post: Best way to test for exception on class's Default Indexer Property
Just do something like this. Action action => () => { var testValue = myClass[5]; } action.ShouldThrow("because...");
View ArticleNew Post: Best way to test for exception on class's Default Indexer Property
That's cool, but how would I cleanly test several related OutOfRangeExceptions in one test? myClass[-1].ShouldThrow... myClass[0].ShouldNotThrow... myClass[1].ShouldThrow... If I define a new action...
View ArticleNew Post: Best way to test for exception on class's Default Indexer Property
Strictly speaking, you shouldn't have multiple assertions in a single test. The 'single assertion per test case' is a general guideline that many experienced TDD practitioners apply. What I would...
View Article