Commented Issue: Support assertions on XML elements [11445]
Support assertions on XElement and XAttributeComments: Associated with changeset 71244.
View ArticleSource code checked in, #71279
Added Should().HaveChild to XDocumentAssertions and XElementAssertions. Added Should().HaveRoot to XDocumentAssertions
View ArticleCommented Issue: Support assertions on XML elements [11445]
Support assertions on XElement and XAttributeComments: Associated with changeset 71279.
View ArticleCommented Issue: Support assertions on XML elements [11445]
Support assertions on XElement and XAttributeComments: Associated with changeset 71308.
View ArticleCreated Issue: Support ComparisonMode.StartWith in validating exception...
Support a new ComparisonMode: 'StartWith' to validate that an exception message starts with a specific text
View ArticleSource code checked in, #71360
Renamed HaveChild into HaveElement for XDocument and XElement assertions
View ArticleCommented Issue: Support assertions on XML elements [11445]
Support assertions on XElement and XAttributeComments: Associated with changeset 71360.
View ArticleSource code checked in, #71415
In case of long string, the error message for string.Should().StartWith() places the actual and expected strings on seperate lines. This makes it easier to find the differences.
View ArticleCommented Issue: Support ComparisonMode.StartWith in validating exception...
Support a new ComparisonMode: 'StartWith' to validate that an exception message starts with a specific textComments: Associated with changeset 71415.
View ArticleSource code checked in, #71416
Implemented ComparisonMode.StartWith and ComparisonMode.StartWithEquivalent for validation of exception messages
View ArticleCommented Issue: Support ComparisonMode.StartWith in validating exception...
Support a new ComparisonMode: 'StartWith' to validate that an exception message starts with a specific textComments: Associated with changeset 71416.
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: ** Comment from web user: bjarke ** The...
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: ** Comment from web user: bjarke ** The impact...
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: ** Comment from web user: dennisdoomen ** I will...
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: ** Comment from web user: bjarke ** Great! Thank...
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 71563.
View ArticleCreated Issue: Error message of TypeAssertions could be more descriptive [11504]
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, #71622
Display the AssemblyQualifiedName when type is not the expected type.
View Article