Quantcast
Channel: Fluent Assertions
Browsing all 1402 articles
Browse latest View live
↧

Closed Issue: Should().NotBeEmpty() enumerates collection twice [10363]

I have a service that returns IEnumerable<T> and enumeration is fairly slow.I am writing a smoke test that just makes sure something is returned:service.GetAll().Should().NotBeEmpty();I see that...

View Article


Closed Issue: Null to null comparison bug. [10262]

string actual = null;string expected = null;actual.Should().Be(expected); // BUG: Expected <null>, but found <null>.Comments:

View Article


Source code checked in, #68514

Added And extension method to TimeSpanConversionExtensions to support 4.Hours().And(30.Minutes())

View Article

Commented Issue: StackOverflowException in BeApproximately for Nullable [11076]

double? value = 4.0;value.Should().BeApproximately(4, 0.001);throws a StackOverflow exceptionComments: Associated with changeset 68514.

View Article

Source code checked in, #68518

Added more TimeSpan extension to support fluently creating a TimeSpan like this: 23.Hours(59.Minutes()).And(20.Seconds());

View Article


Commented Issue: StackOverflowException in BeApproximately for Nullable [11076]

double? value = 4.0;value.Should().BeApproximately(4, 0.001);throws a StackOverflow exceptionComments: Associated with changeset 68518.

View Article

Source code checked in, #68519

View Article

Commented Issue: StackOverflowException in BeApproximately for Nullable [11076]

double? value = 4.0;value.Should().BeApproximately(4, 0.001);throws a StackOverflow exceptionComments: Associated with changeset 68519.

View Article


Source code checked in, #68529

Enabled code coverage

View Article


Commented Issue: StackOverflowException in BeApproximately for Nullable [11076]

double? value = 4.0;value.Should().BeApproximately(4, 0.001);throws a StackOverflow exceptionComments: Associated with changeset 68529.

View Article

Commented Issue: Add .BeNull() and .BeNotNull() assertions for nullable types...

Hi,could you add .BeNull() and .BeNotNull() assertions for Nullable types, please?ThanlsComments: ** Comment from web user: jesuissur ** We should probably add documentation about nullable types. I had...

View Article

Updated Wiki: Documentation

Supported Test Frameworks Fluent Assertions supports MSTest, NUnit and XUnit. Starting with version 1.3.0, you can simply add a reference to the corresponding test framework assembly to the unit test...

View Article

Commented Issue: Add .BeNull() and .BeNotNull() assertions for nullable types...

Hi,could you add .BeNull() and .BeNotNull() assertions for Nullable types, please?ThanlsComments: ** Comment from web user: jesuissur ** Actually, it is documented under the IComparable types...

View Article


New Post: Customizing reason display

Hi there, when using Should()... with a reason and reason parameters, is there any way to get Fluent Assertions to just throw the formatted reason as the assertion exception message, and not try to...

View Article

Created 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 Article


Source code checked in, #68942

Added contribution from Urs Enzler to support MSpec

View Article

Created 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 Article


Source code checked in, #68981

Added support for ComparisonMode in the WithInnerMessage method of ExceptionAssertions.

View Article

Commented 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.Comments: Associated with...

View Article

Created 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 Article
Browsing all 1402 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>