Closed Issue: StackOverflowException in BeApproximately for Nullable [11076]
double? value = 4.0;value.Should().BeApproximately(4, 0.001);throws a StackOverflow exception
View ArticleClosed Issue: ShouldFirePropertyChanged error message does not include...
When ShouldFirePropertyChanged fails the error message does not include which property it is.See my patch that corrects this.
View ArticleClosed Issue: CollectionAssertions.Equal doesn't validate that collections...
The following test should fail because the second collection has fewer elements than the first, but it doesn't [Test] public void...
View ArticleClosed Feature: Support ComparisonMode in the...
ComparisonMode is now only supported in the WithMessage method of the ExceptionAssertions. It would be consistent to have it available in the WithInnerMessage method as well.
View ArticleClosed Feature: Property comparison / Recursive on complex types [11112]
When we use the ShouldHave (property comparison), it would be nice if, when the comparison of two properties (of complex types) are not the same type, cannot be converted and are not equal, the method...
View ArticleClosed Issue: StackoverflowException with Should().Contain(Expression...
I´m getting a StackOverflowException when i use the Should.Contain on a collection specifying a predicate to evaluate. Here´s my unittest that throws the exception.The same is true for NotContain using...
View ArticleClosed Issue: StackOverflowException while formatting error message [11172]
When for example two objects reference each other over properties and FluentAssertions wants to build an error message then the DefaultValueFormatter causes a StackoverflowException because it loops...
View ArticleClosed Issue: Add .BeNull() and .BeNotNull() assertions for nullable types...
Hi,could you add .BeNull() and .BeNotNull() assertions for Nullable types, please?Thanls
View ArticleClosed Issue: Event Monitored objects are never released [11136]
Objects that are monitored using .MonitorEvents() are kept in memory forever. In huge projects this results in OutOfMemory exception when running unit tests.
View ArticleUpdated Wiki: Temporary Post Used For Theme Detection...
This is a temporary post that was not deleted. Please delete this manually. (d94de5bb-a6ec-4c57-8a18-1fa38b7d89b2 - 3bfe001a-32de-4114-a6b4-4005b770f6d7)
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 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 ArticleNew Post: C# vs VB.NET difference in ShouldHave().AllProperties().EqualTo() ?
Do'h! When I wrote my original message, I had missed the public property on the reference of class 1 in my C# code. Hence the test passed.My bad, so sorry! I saw FA 1.6 was just released but could not...
View ArticleNew Post: C# vs VB.NET difference in ShouldHave().AllProperties().EqualTo() ?
No problem. It is indeed part of FA 1.6.0. You need to include the method call IncludingNestedObjects() as in object.ShouldHave().AllProperties().IncludingNestedObjects().EqualTo(anotherObject);
View ArticleNew Post: C# vs VB.NET difference in ShouldHave().AllProperties().EqualTo() ?
Hmmm... Am I missing something? I still don't get it to work. [TestMethod]public void TestMethod1(){ ClassOne c1 = new ClassOne(); ClassOne c2 = new ClassOne();...
View ArticleNew Post: C# vs VB.NET difference in ShouldHave().AllProperties().EqualTo() ?
I'll have to look into that specific example.
View ArticleNew Post: C# vs VB.NET difference in ShouldHave().AllProperties().EqualTo() ?
Alright, seems like the most basic of basic examples though, so I'm guessing I'm doing something wrong, no?
View ArticleNew Post: C# vs VB.NET difference in ShouldHave().AllProperties().EqualTo() ?
You're right. Its indeed a bug in FA. Checking it out now.
View ArticleCreated Issue: Recursive property comparison not always working as expecting...
See http://fluentassertions.codeplex.com/discussions/277551
View Article