Equalsverifier fails on enum

[GoogleCodeExporter]

What steps will reproduce the problem?
1. implement an enum (without equals method)
2. run equalsverifier on it
3. you will get identical-copy and symmetry warning
4. you will need to use 
EqualsVerifier.forClass(myclass).withRedefinedSuperclass().suppress(Warning.IDEN
TICAL_COPY).verify();

I would expect equalsverifier to work out-of-the-box for enums that don't 
overwrite equals()

Original issue reported on code.google.com by [email protected] on 8 Mar 2014 at 11:23

[GoogleCodeExporter]

I never implemented this because Java itself guarantees that enums always have 
a correct equals implementation. In fact, you can't even override equals in an 
enum. Using EqualsVerifier to verify that, always seemed a bit pointless to me.
That said, it would be easy enough to fix this.

What use case do you have for this?

Original comment by [email protected] on 9 Mar 2014 at 10:43

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

My use case is, that I provide an annotated base-class for all my unit-tests. 
It has (amongst other things) a testEqualsContract which is executed for all 
subclasses and thus for all my test-cases.
This works fine for most of my test-cases, but not for those testing enums. In 
those I need to overwrite that method with the mentioned "work-around"

Original comment by [email protected] on 9 Mar 2014 at 9:21

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

OK, that makes sense. I'll fix this in the next release.
Thanks for reporting it!

Original comment by [email protected] on 10 Mar 2014 at 9:37

• Changed state: Accepted
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Thanks for accepting it :-)
Btw. the same would be the case for classes not implementing hashCode/equals 
(have not yet fallen into that pit :-) )

Original comment by [email protected] on 10 Mar 2014 at 10:51

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I've been thinking about that too, but unfortunately it conflicts with Issue 66.
I could add a flag though, so that it also works for this scenario. I'll think 
about it :).

Original comment by [email protected] on 11 Mar 2014 at 11:51

• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

I've fixed the enum part in version 1.4.1 which I've just released. The object 
part, I'll leave for another time.

Original comment by [email protected] on 18 Mar 2014 at 11:40

• Changed state: Fixed
• Added labels: ****
• Removed labels: ****

[GoogleCodeExporter]

Perfect - thanks :-)

Original comment by [email protected] on 18 Mar 2014 at 5:21

• Added labels: ****
• Removed labels: ****