Can anybody summarize differences and usage scope between them?
I read SO articles,
In my humble understanding, ShouldBeEquivalientTo()
and Should().BeEquivalentTo()
work similar if Should().BeEquivalentTo()
does in-depth comparison.
I agree this is confusing. Should().BeEquivalentTo()
should actually be called Should().EqualInAnyOrder()
or something like that. As you said, it uses the Equals
implementation of the involved objects to see if all of the ones in the expected
collection appear in the actual
collection, regardless of order. I'll need to fix that for the next major version.