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

Source code checked in, #67150

Refactored the property comparison assertions to use the correct assertion class for the individual properties. This gives the same kind of detailed reports for properties as you get for the individual...

View Article


Commented Issue: Property comparison should be a bit smarter [10683]

The ShouldHave().AllProperties() and corresponding variants should not just use the Equals() method to compare individual properties, but attempt to use the built-in .Be()/.Equal() extension methodes...

View Article


Source code checked in, #67151

Refactored StringEqualityValidator to comply to Clean Code

View Article

Commented Issue: Property comparison should be a bit smarter [10683]

The ShouldHave().AllProperties() and corresponding variants should not just use the Equals() method to compare individual properties, but attempt to use the built-in .Be()/.Equal() extension methodes...

View Article

Source code checked in, #67167

Property comparison throws with a clear explanation when property types are incompatible

View Article


Commented Issue: Property comparison should be a bit smarter [10683]

The ShouldHave().AllProperties() and corresponding variants should not just use the Equals() method to compare individual properties, but attempt to use the built-in .Be()/.Equal() extension methodes...

View Article

Source code checked in, #67300

Refactored property comparison into a dedicated validator class.

View Article

Commented Issue: Property comparison should be a bit smarter [10683]

The ShouldHave().AllProperties() and corresponding variants should not just use the Equals() method to compare individual properties, but attempt to use the built-in .Be()/.Equal() extension methodes...

View Article


Source code checked in, #67315

When a string argument contains a newline or is longer than 6 characters, both the expected and the actual strings are displayed on a new line for easy visual comparison.

View Article


Commented Issue: Improve exception message for string.Should.Be(multiple...

The current exception when strings are not equal is:Expected "bc", but "a" is too short.This works well when the excepted and actual value are not multiple lines; ie do not have...

View Article

Source code checked in, #67345

Replaced < and > from indicating collections with the more common { and }

View Article

Source code checked in, #67351

Moved formatting of values to a dedicated class and removed the embracing <> when displaying numbers.

View Article

Source code checked in, #67352

Ensured that items within a collection are also formatted properly

View Article


Source code checked in, #67354

Added an extra spec to make sure enumerables of enumerables were reported properly.

View Article

Source code checked in, #67548

The default formatter will display the object structure like this: MyClass { Property1 = blah } But only if the object does not implement ToString()

View Article


Created Issue: current IComparable asserts aren't available for IComparable...

same as the title, don't really think I can add much more,btw, started using your library today, and so far loving it, great work.

View Article

Commented Issue: current IComparable asserts aren't available for IComparable...

same as the title, don't really think I can add much more,btw, started using your library today, and so far loving it, great work.Comments: ** Comment from web user: dennisdoomen ** Thanks!Do you mean...

View Article


Commented Issue: current IComparable asserts aren't available for IComparable...

same as the title, don't really think I can add much more,btw, started using your library today, and so far loving it, great work.Comments: ** Comment from web user: keivanbeigi ** Yes, I'm moving from...

View Article

New Post: Should Assertion Library or FluentAssertions

I'm a little bit perplexed about what seems to me identical goals of this library (FluentAssertions) and the Sould Assertion Library (http://should.codeplex.com). Is there any valid reason to use one...

View Article

Created Issue: Test framework detection not working [11012]

Instead of trying to detect the framework using Assembly.Load Method, we should use something like thisAppDomain.CurrentDomain.GetAssemblies().Any(a => a.GetName().Name =...

View Article
Browsing all 1402 articles
Browse latest View live


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