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

Commented Issue: FluentAssertions with Continuous Integration [11205]

it would be nice to have FluentAssertions on a CI environment so that everyone can get the latest and greatest build with correct versioning without having to build it manually.If you'd like, I can get...

View Article


Commented Issue: FluentAssertions with Continuous Integration [11205]

it would be nice to have FluentAssertions on a CI environment so that everyone can get the latest and greatest build with correct versioning without having to build it manually.If you'd like, I can get...

View Article


New Post: Can not use double.Should().Be(double)

Hello , would it be possible to change AssertionExtensions in order to support  double.Should().Be(double)?    This: public static NumericAssertions<double?> Should(this double? actualValue);...

View Article

Source code checked in, #69889

PropertyInfoAssertions implemented

View Article

Commented Issue: Support for validating attributes [11231]

I recognize that this may not be an extremely frequent need, but when building some MVC sites, I have determined that I require my POST commands to include the ValidateAntiForgeryToken attribute.I...

View Article


Commented Issue: Support for validating attributes [11231]

I recognize that this may not be an extremely frequent need, but when building some MVC sites, I have determined that I require my POST commands to include the ValidateAntiForgeryToken attribute.I...

View Article

Created Issue: Hangs the Resharper Test Runner while theory is introduced...

Test cases is always in pending state when Theory test case is introduced.e.g. the following test case hangs the test runner [Theory] [InlineData(5, 0, 3, 3, 0)] [InlineData(5, 0, 9, 5, 4)]...

View Article

Source code checked in, #69909

Refactored the comparison mode for excpetion messages into a helper class. Some minor changes while reviewing

View Article


Source code checked in, #69911

Also refactored the assertion of inner exception messages

View Article


Source code checked in, #69912

Added an extra spec around inner exception messages

View Article

Source code checked in, #69922

Added support for checking the inner exception message using case-insensitive ComparisonModes

View Article

Source code checked in, #69924

Various minor XML comment fixes and naming improvements. Renamed CyclicReferenceTracker to ObjectTracker. Refactored several earlier checkins.

View Article

Source code checked in, #70007

Added Before and After extensions methods for TimeSpans

View Article


Commented Issue: Add support for Guids [11137]

See patch provided by marcoerni.Comments: Associated with changeset 70007.

View Article

Created Issue: ShouldContainInOrder and not unique items [11292]

Considernew[] { 1, 2, 2, 3 }.Should().ContainInOrder(new[] { 1, 2, 3 });Should that be passing or failing?And what about new[] { 1, 2, 3, 2 }.Should().ContainInOrder(new[] { 1, 2, 3 });I'm not sure...

View Article


Commented Issue: ShouldContainInOrder and not unique items [11292]

Considernew[] { 1, 2, 2, 3 }.Should().ContainInOrder(new[] { 1, 2, 3 });Should that be passing or failing?And what about new[] { 1, 2, 3, 2 }.Should().ContainInOrder(new[] { 1, 2, 3 });I'm not sure...

View Article

Commented Issue: Hangs the Resharper Test Runner while theory is introduced...

Test cases is always in pending state when Theory test case is introduced.e.g. the following test case hangs the test runner [Theory] [InlineData(5, 0, 3, 3, 0)] [InlineData(5, 0, 9, 5, 4)]...

View Article


Source code checked in, #70338

Exclude special methods like 'add_*', 'remove_*' in the MethodInfoSelector

View Article

Commented Issue: Support for validating attributes [11231]

I recognize that this may not be an extremely frequent need, but when building some MVC sites, I have determined that I require my POST commands to include the ValidateAntiForgeryToken attribute.I...

View Article

Created Issue: Calling Should().Be() on a different type causes a...

var a = new ObjectA();var b = new ObjectB();a.Should().Be(b);This is of course a syntactical error, but causing a StackOverflowException to be thrown isn't the best way to handle it either.

View Article
Browsing all 1402 articles
Browse latest View live


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