Skip to content
New issue

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

EqualsVerifier gives false positive common error (using == instead of .equals()) #104

Closed
GoogleCodeExporter opened this issue Mar 29, 2015 · 10 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.  I used == instead of .equals when comparing two fields.
2.
3.


What is the code (equals method, hashCode method, relevant fields) that
triggers the problem?
I've attached a full example.

What error message does EqualsVerifier give?
None.

What stacktrace does EqualsVerifier print, when called with the debug()
method?


What did you expect?
Unit test failure, as shown in the "by hand" test.


What version of EqualsVerifier are you using?
1.6


Please provide any additional information below.


Original issue reported on code.google.com by dcorbi...@gmail.com on 8 Feb 2015 at 3:57

Attachments:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant