Fix equality checking of Comparable Mocks #1323
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
EqualArgumentConstraint
usesDefaultTypeTransformation.compareEqual
to check arguments' equality in interactions. For most objects, this is
equivalent to calling
.equals
, so Java Mocks come with an intuitivedefault implemention of
.equals
. But for objects that areComparable
(including Mocks of types that implement
Comparable
),DefaultTypeTransformation.compareEqual(x, y)
is equivalent to callingx.compareTo(y) == 0
. As a result, all Mocks of Comparable types aretreated as equal by
EqualArgumentConstraint
.This commit fixes that by adding a default implementation of
.compareTo
toComparable
Mocks.