Reviewed: Release 2.0.1 (Jun 25, 2013)
Rated 5 Stars (out of 5) - I've been using Fluent Assertions for a couple of years now and pulling it down from Nuget has become as automatic for me as creating the test project itself.
View ArticleCommented 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 ArticleCommented Issue: add new string assertion .Should().BeInFormat(format, args)...
This is similar to wildcards, but I think it will be useful too. If maintainers says ok for that I will be happy to contribute an implementation.Comments: Could you please explain what the method...
View ArticleCreated Unassigned: XElement .Should().Be() gives false positives. [12494]
The current implementation of the Be assertion for XElement is implemented in such a way as to cause apparent false positive tests. It only checks the element names, but other Be() assertions in...
View ArticleCommented Unassigned: XElement .Should().Be() gives false positives. [12494]
The current implementation of the Be assertion for XElement is implemented in such a way as to cause apparent false positive tests. It only checks the element names, but other Be() assertions in...
View ArticleCommented Unassigned: XElement .Should().Be() gives false positives. [12494]
The current implementation of the Be assertion for XElement is implemented in such a way as to cause apparent false positive tests. It only checks the element names, but other Be() assertions in...
View ArticleCommented Unassigned: XElement .Should().Be() gives false positives. [12494]
The current implementation of the Be assertion for XElement is implemented in such a way as to cause apparent false positive tests. It only checks the element names, but other Be() assertions in...
View ArticleCommented Unassigned: XElement .Should().Be() gives false positives. [12494]
The current implementation of the Be assertion for XElement is implemented in such a way as to cause apparent false positive tests. It only checks the element names, but other Be() assertions in...
View ArticleNew Post: Support for C# Dynamics
For me both - static equivalent and declaring test item as an object work fine.
View ArticleCreated Unassigned: Collection should contain other collection behaving...
I want to assert that a collection of simple objects includes a smaller collection of the same object type. For some reason actualCollection.Should().Contain(expectedCollection) is failing with a...
View ArticleCommented Unassigned: Collection should contain other collection behaving...
I want to assert that a collection of simple objects includes a smaller collection of the same object type. For some reason actualCollection.Should().Contain(expectedCollection) is failing with a...
View ArticleCommented Unassigned: Collection should contain other collection behaving...
I want to assert that a collection of simple objects includes a smaller collection of the same object type. For some reason actualCollection.Should().Contain(expectedCollection) is failing with a...
View ArticleEdited Feature: Show details about an AggregateException in ShouldNotThrow...
When an AggregateException is thrown it would be nice if ShouldNotThrow shows the details about the inner exception. Now you only see that an AggregateException is thrown, but is is more interesting to...
View ArticleEdited Issue: Inconsistent ShouldBeEquivalentTo() behaviour for collections...
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: Extend ShouldThrow*() to Func [12148]
Extend the ShouldThrow*() methods for Func<Task> too so you can work with async methods:Func<Task> foo = async () => { await DoSthAsync();...
View ArticleCommented Issue: Extend ShouldThrow*() to Func [12148]
Extend the ShouldThrow*() methods for Func<Task> too so you can work with async methods:Func<Task> foo = async () => { await DoSthAsync();...
View ArticleCreated Unassigned: Assembly not correctly loaded in Mono 3.2.0 [12496]
It seems that a project that references FluentAssertions.dll is not correctly loaded in Xamarin Studio 4.0 (on Mac OS X).If I remove the reference and I'm also unable to install it with NuGet Package...
View ArticleCommented Unassigned: Assembly not correctly loaded in Mono 3.2.0 [12496]
It seems that a project that references FluentAssertions.dll is not correctly loaded in Xamarin Studio 4.0 (on Mac OS X).If I remove the reference and I'm also unable to install it with NuGet Package...
View ArticleCommented Unassigned: Assembly not correctly loaded in Mono 3.2.0 [12496]
It seems that a project that references FluentAssertions.dll is not correctly loaded in Xamarin Studio 4.0 (on Mac OS X).If I remove the reference and I'm also unable to install it with NuGet Package...
View Article