Clik here to view.
Updated Wiki: Home
Project Description Fluent 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...
View ArticleClik here to view.
Updated Wiki: Home
Project Description Fluent 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...
View ArticleUpdated Wiki: Temporary Post Used For Theme Detection...
This is a temporary post that was not deleted. Please delete this manually. (13389238-c4d2-466f-a886-d0c3655d1a79 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)
View ArticleSource code checked in, #5917d76e4bcd
Merge branch 'Release-2.0' Conflicts: Main/FluentAssertions.Net35/FluentAssertions.Net35.csproj Main/FluentAssertions.Net40/FluentAssertions.Net40.csproj...
View ArticleNew Post: Optional arguments in 2.0 break method usage in expressions
Congratulations on the 2.0 release - some really exciting new features in there! I have one complaint however :-( All overloads that took the reason and reasonargs parameters have been removed and...
View ArticleNew Post: Optional arguments in 2.0 break method usage in expressions
Hi Adam, Thanks for taking the time to explain your problem. I've been in that same 'camp', at least, until recently. My C# Coding Guidelines still recommend not doing that, but since its introduction...
View ArticleNew Post: Equals cannot match generic List correctly
I just upgraded to 2.0 and I have following code to test list values actualResponse.MyObject.Group .Should().NotBeEmpty() .And.Should().NotBeNull() .And.Should().Equals(new List<string> {...
View ArticleNew Post: Equals cannot match generic List correctly
Hi Hardywang, I think your problem is caused by the fact that you are using Equals() rather than Equal(). You are now calling the built-in Object.Equals method every object inherits from System.Object.
View ArticleNew Post: Optional arguments in 2.0 break method usage in expressions
Hi Dennis, After giving it some thought, I think I may just remove the Expression overloads from xBehave.net. It was fun code to write, but I only ever gave it 'experimental' status in the...
View ArticleNew Post: Optional arguments in 2.0 break method usage in expressions
Pfew, I really wasn't looking forward to all that work :-) But seriously, thanks for the trust and compliments. That's what keeps open-source projects fun.
View ArticleCommented Issue: HaveElement should support XNames [12453]
See discussion http://stackoverflow.com/questions/12099510/how-to-test-xelement-and-its-child-elementsComments: Playing with this one on the fork:...
View ArticleNew Post: Comparing two similar objects fails
Hi, when i'm comparing two matching objects, the assertion fails. any idea why? Expected property InFieldOffset to be Data.Recipe.FieldOffset { Column = 1 Row = 1 }, but found...
View ArticleSource code checked in, #3e69c694b236
Ensured that the WinRT unit test assembly is excluded from the nuget package.
View Article