What are ways to keep hashCode/equals consistent with the business definition of the class?

Question

Object javadocs and Josh Bloch tell us a great deal about how hashCode/equals should be implemented, and good IDEs will handle fields of various types correctly. Some discussio

Answer 1

You could serialize your objects to a string using a tool that finds your properties using reflection (XStream, for example), and store that string in a repository. Your unit tests could re-serialize your objects and compare the results to your stored values.

As part of your own process, make the storage of those strings contingent on manually validating that your hashCode and equals correctly capture all relevant values.