You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A Matcher that test equals() in both directions and also compares hashCode() could come useful when testing equals() and hashCode() implementations.
In fact, most rules from the contract, except the transitiveness could be checked in the the Matcher:
It is reflexive: for any non-null reference value x, x.equals(x) should return true.
It is symmetric: for any non-null reference values x and y, x.equals(y) should return true if and only if y.equals(x) returns true.
It is transitive: for any non-null reference values x, y, and z, if x.equals(y) returns true and y.equals(z) returns true, then x.equals(z) should return true.
It is consistent: for any non-null reference values x and y, multiple invocations of x.equals(y) consistently return true or consistently return false, provided no information used in equals comparisons on the objects is modified.
For any non-null reference value x, x.equals(null) should return false.
The text was updated successfully, but these errors were encountered:
A
Matcher
that testequals()
in both directions and also compareshashCode()
could come useful when testingequals()
andhashCode()
implementations.In fact, most rules from the contract, except the transitiveness could be checked in the the
Matcher
:The text was updated successfully, but these errors were encountered: