The
Assert.AreEqual() is improperly implemented, i.e. it gives precedence to IEnumerable<>
which is used along with SequenceEquals() which is wrong.
That makes testing unpredictable in many places where some class may change interface and
that would completely silently change all of the unit tests meanings.
ArEqual() must use object.Equal only.
The Assert.AreEqual() is improperly implemented, i.e. it gives precedence to IEnumerable<> which is used along with SequenceEquals() which is wrong.
That makes testing unpredictable in many places where some class may change interface and that would completely silently change all of the unit tests meanings. ArEqual() must use object.Equal only.