Clik here to view.
Updated Wiki: Home
Project DescriptionFluent Assertions is a set of .NET extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style test. We currently use it in all our internal...
View ArticleClik here to view.
Updated Wiki: Home
Project DescriptionFluent Assertions is a set of .NET extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style test. We currently use it in all our internal...
View ArticleClik here to view.
Updated Wiki: Home
Project DescriptionFluent Assertions is a set of .NET extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style test. We currently use it in all our internal...
View ArticleClik here to view.
Updated Wiki: Home
Project DescriptionFluent Assertions is a set of .NET extension methods that allow you to more naturally specify the expected outcome of a TDD or BDD-style test. We currently use it in all our internal...
View ArticleCreated Unassigned: CollectionAssertions.Equal does not handle null properly...
I have the following situation:string[] expected = null;string[] result = null;result.Should().Equal(expected) // Throws Exception"Expected collection to be equal, but found <null>."Since the...
View ArticleCommented Issue: Inconsistent ShouldBeEquivalentTo() behaviour for...
I'm having trouble comparing lists of objects that come back in an indeterminate order. I thought `ShouldBeEquivalentTo()` would take care of this for me, but it doesn't seem to :(Check out the...
View ArticleCommented Issue: Inconsistent ShouldBeEquivalentTo() behaviour for...
I'm having trouble comparing lists of objects that come back in an indeterminate order. I thought `ShouldBeEquivalentTo()` would take care of this for me, but it doesn't seem to :(Check out the...
View ArticleCommented Issue: Inconsistent ShouldBeEquivalentTo() behaviour for...
I'm having trouble comparing lists of objects that come back in an indeterminate order. I thought `ShouldBeEquivalentTo()` would take care of this for me, but it doesn't seem to :(Check out the...
View ArticleCommented Issue: Inconsistent ShouldBeEquivalentTo() behaviour for...
I'm having trouble comparing lists of objects that come back in an indeterminate order. I thought `ShouldBeEquivalentTo()` would take care of this for me, but it doesn't seem to :(Check out the...
View ArticleCommented Unassigned: CollectionAssertions.Equal does not handle null...
I have the following situation:string[] expected = null;string[] result = null;result.Should().Equal(expected) // Throws Exception"Expected collection to be equal, but found <null>."Since the...
View ArticleNew Post: Why did you add the And property?
I feel like it's making things far more complicated and less fluent, I don't even consider that to be readable, so my question is why the verbosity? do you have plans to change it? In fact, to be...
View ArticleNew Post: Why did you add the And property?
Yeah, it's one of those features that I don't really like anymore. In fact, I haven't even used it myself. At that time it sounded like a good idea. But when I recently offered to remove it completely,...
View ArticleReviewed: Release 2.0.1 (May 28, 2013)
Rated 5 Stars (out of 5) - Stupendous project, it's a required dependency for all my test projects. Should be rolled into .Net like JSON.Net
View ArticleCreated Unassigned: BeEmpty() on a byte array [12491]
imho empty on a byte array means that all bytes is zero, not that the actual length is zero. The method isn't very useful otherwise as it's quite easy to write Buffer.Count.Should.Be(0);
View ArticleCommented Unassigned: BeEmpty() on a byte array [12491]
imho empty on a byte array means that all bytes is zero, not that the actual length is zero. The method isn't very useful otherwise as it's quite easy to write Buffer.Count.Should.Be(0);Comments: The...
View ArticleCreated Unassigned: Equal and collections of generics = bad message...
If a Equal test fail on a collection containing generic types (Class<T>) the test failed message returns a generic error message, telling just the index of the collection were the test failed,...
View ArticleCommented Unassigned: Equal and collections of generics = bad message...
If a Equal test fail on a collection containing generic types (Class<T>) the test failed message returns a generic error message, telling just the index of the collection were the test failed,...
View ArticleNew Post: OnlyContainItemsOfType method does not exist
The latest version of FluentAssertions (v2.0.1) does not contain a method OnlyContainItemsOfType<T> specified in the documentation. Is this method planned for the future version or was it already...
View ArticleNew Post: OnlyContainItemsOfType method does not exist
It's still there, but it was renamed to ContainItemsAssignableTo<T>().... Regards, Dennis
View ArticleCreated Unassigned: Print x.0 when x is is a double/float representing a...
I certainly will understand if this does not get picked up since there are a lot of other similar situations that would not be as easy to fix, but it would be a nice-to-have so I thought I would throw...
View Article