test(apollo-client): use assertEquals instead of assertThat #3667
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 the purpose of this PR
Fix test fail when use java 9 or above.
Which issue(s) this PR fixes:
NONE
Brief changelog
Use equals to compare properties directly.
Follow this checklist to help us incorporate your contribution quickly and easily:
mvn clean test
to make sure this pull request doesn't break anything.details
Consider code like follow
In Jdk 8, the output will be
But in Jdk 9 or above, the output will change to
One can run it on website https://www.jdoodle.com/online-java-compiler/
So it need to compare properties directly instread of using entrySet.