fix: assertj contains is weaker than hamcrests contains #371
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.
What's changed?
Hamcrest's
contains
matches AssertJ'scontainsExactly
. AssertJscontains
does not care about order and completeness. Hamcrestscontains
does, see the docs!What's your motivation?
Fix this bug.
Anything in particular you'd like reviewers to focus on?
Should I create an issue or is just the pr fine?
Another topic: I am not so sure about the mapping of containsInRelativeOrder to containsExactly as I don't know how
containsInRelativeOrder
works. From the docs I don't understand if it matches for completeness in both directions. Kind of related to this pr, but also a different topic.Anyone you would like to review specifically?
no
Have you considered any alternatives or workarounds?
It is a bug to me.
Any additional context
Checklist
./gradlew licenseFormat