Commented Issue: Test framework detection using assembly scanning is case...
LateBoundTestFramework checks if an assembly with the given name is loaded. But the check is case sensitive. Therefore in our case the NUnit cannot be determined - NUnitTestFramework defines...
View ArticleEdited Issue: Add NotStartWith and NotEndWith methods [12441]
Add NotEndWith, NotStartWith, NotEndWithEquivalent and NotStartWithEquivalent.
View ArticleCommented Issue: Test framework detection using assembly scanning is case...
LateBoundTestFramework checks if an assembly with the given name is loaded. But the check is case sensitive. Therefore in our case the NUnit cannot be determined - NUnitTestFramework defines...
View ArticleNew Post: Why so many negation methods?
Yeah you can either do it.Should().Not().BeWhatever() or it.ShouldNot().BeWhatever(), obviously there are few options here but instead of introducing a breaking change, I'd imagine you can create 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 ArticleNew Post: Exception in Excluding from nested property.
hi I tried exclude from test one property how writing in Docs: orderDto.ShouldBeEquivalentTo(order, options => options.Excluding(o => o.Products[1].Status)); My classes:public class Product {...
View ArticleNew Post: Exception in Excluding from nested property.
I think using an Expression with an indexer only works if the collection is an array. You should use the overload that takes a Func<ISubjectInfo, bool>() to compare the property path against...
View ArticleNew Post: Exception in Excluding from nested property.
dennisdoomen wrote: I think using an Expression with an indexer only works if the collection is an array. You should use the overload that takes a Func<ISubjectInfo, bool>() to compare the...
View ArticleNew Post: Exception in Excluding from nested property.
Then you need the other overload and use the string-representation of the PropertyPath property on ISubjectInfo.
View ArticleNew Post: Exception in Excluding from nested property.
dennisdoomen wrote: Then you need the other overload and use the string-representation of the PropertyPath property on ISubjectInfo. You can a sample please? Thanks.
View ArticleEdited Issue: Add NotStartWith and NotEndWith methods [12441]
Add NotEndWith, NotStartWith, NotEndWithEquivalent and NotStartWithEquivalent.
View ArticleClosed Issue: Nullable does not provide BeNull() extensions [12459]
The extension methods available for asserting the state of a Nullable<Guid> value only cater for the Guid type and not the nullable condition. I expected that I could assert that the value either...
View ArticleCommented Issue: FluentAssertions 2.0: objects, which are inherited from...
In our project we have classes inherited from collections. These classes have own properties and we should compare their instances only by specified properties and ignore data in collections. But the...
View ArticleClosed Issue: FluentAssertions 2.0: objects, which are inherited from...
In our project we have classes inherited from collections. These classes have own properties and we should compare their instances only by specified properties and ignore data in collections. But the...
View ArticleEdited Feature: String comparison with 'ignore whitespace' [12423]
The "Should().BeEquivalentTo()" ignores casing, but it would be great to have an option for ignoring whitespace and tab/carriage return/newline characters as well
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 ArticleEdited Issue: DateTimeOffset support [12464]
It would be great if FA supported DateTimeOffset in the same way it supported DateTime.
View ArticleCreated Issue: WP8: Extend ShouldThrow() to Func [12485]
As fixed for the issue below in WinRT: http://fluentassertions.codeplex.com/workitem/12148It would be really useful to be fixed as well for Windows Phone 8. Most of the functionality is also async, so...
View ArticleEdited Issue: WP8: Extend ShouldThrow() to Func [12485]
As fixed for the issue below in WinRT: http://fluentassertions.codeplex.com/workitem/12148It would be really useful to be fixed as well for Windows Phone 8. Most of the functionality is also async, so...
View Article