We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Note: only the latest version is supported
All known (confirmed in 7.3.0 and in master branch as at 25 May 2023)
If two maps contain different keys, they should never be reported as equal.
If two maps contain different keys, if the values for all such keys in the LHS map are null, they are reported as equal.
Everywhere I believe.
Please, share the test case (as small as possible) which shows the issue
Map<String,Object> map1 = new LinkedHashMap<>(); map1.put("a", 1); map1.put("b", null); Map<String,Object> map2 = new LinkedHashMap<>(); map2.put("a", 1); map2.put("c", null); Assert.assertEquals(map1, map2);
The above assertion passes, but clearly it shouldn't.
Incase you plan to raise a pull request to fix this issue, please make sure you refer our Contributing section for detailed set of steps.
I will open a fix shortly.
The text was updated successfully, but these errors were encountered:
Fixed by PR #2914
Test case checkMapNotEqualsWithNull added failing in 7a4394b passing once fixed applied in 4216a3d .
checkMapNotEqualsWithNull
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
TestNG Version
All known (confirmed in 7.3.0 and in master branch as at 25 May 2023)
Expected behavior
If two maps contain different keys, they should never be reported as equal.
Actual behavior
If two maps contain different keys, if the values for all such keys in the LHS map are null, they are reported as equal.
Is the issue reproducible on runner?
Everywhere I believe.
Test case sample
The above assertion passes, but clearly it shouldn't.
Contribution guidelines
I will open a fix shortly.
The text was updated successfully, but these errors were encountered: