Commented Issue: Error message of TypeAssertions could be more descriptive...
When the expected type is the same as the actual type, but from a different assembly, the error message does not point you in that direction. It just states"Expected type to be MyNamespace.MyType, but...
View ArticleSource code checked in, #71623
Only show AssemblyQualifiedName in type assertions error message if FullName of types is the same
View ArticleCommented Issue: Error message of TypeAssertions could be more descriptive...
When the expected type is the same as the actual type, but from a different assembly, the error message does not point you in that direction. It just states"Expected type to be MyNamespace.MyType, but...
View ArticleSource code checked in, #71631
Applied the AssemblyQualifiedName in ObjectAssertions.BeOfType<T> failure message
View ArticleCommented Issue: Error message of TypeAssertions could be more descriptive...
When the expected type is the same as the actual type, but from a different assembly, the error message does not point you in that direction. It just states"Expected type to be MyNamespace.MyType, but...
View ArticleSource code checked in, #71645
Added unit test for BeOfType failure message with AssemblyQualifiedNames
View ArticleCommented Issue: Error message of TypeAssertions could be more descriptive...
When the expected type is the same as the actual type, but from a different assembly, the error message does not point you in that direction. It just states"Expected type to be MyNamespace.MyType, but...
View ArticleCommented Issue: Support assertions on XML elements [11445]
Support assertions on XElement and XAttributeComments: Associated with changeset 71646.
View ArticleSource code checked in, #71647
Disabled warnings for conflicting types in specs where that was the intention
View ArticleCommented Issue: Error message of TypeAssertions could be more descriptive...
When the expected type is the same as the actual type, but from a different assembly, the error message does not point you in that direction. It just states"Expected type to be MyNamespace.MyType, but...
View ArticleSource code checked in, #71648
Added deeper detectection of cyclic references while recursively comparing properties or generating a string representation of an object graph
View ArticleCommented Feature: Support property comparison of objects in collections [11447]
If a property is of a collection type of another object, and recursive comparison is enabled, it should compare the individual objects as well.Comments: Associated with changeset 71648.
View ArticleCreated Feature: Support filtering types from an assembly by their namespace...
Allow for:assembly.Types().UnderNamespace("Core.Domain")
View ArticleCommented Feature: Support filtering types from an assembly by their...
Allow for:assembly.Types().UnderNamespace("Core.Domain")Comments: Associated with changeset 71675.
View ArticleCommented 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 ArticleCommented Task: Create A4 cheat sheet [10813]
Create an A4-sized cheat sheet with an overview of the supported extension syntax.Comments: ** Comment from web user: ursenzler ** I'm currently trying to put the features on a A4 sheet, but there's...
View ArticleCommented Task: Create A4 cheat sheet [10813]
Create an A4-sized cheat sheet with an overview of the supported extension syntax.Comments: ** Comment from web user: ursenzler ** I can condens it onto a double side, see attachment. It's a Draft, let...
View ArticleCommented Task: Create A4 cheat sheet [10813]
Create an A4-sized cheat sheet with an overview of the supported extension syntax.Comments: ** Comment from web user: dennisdoomen ** Awesome. Looks like it took a lot of time to create. I was actually...
View Article