When you have a large domain with many classes that all have
equals methods to be tested, using EqualsVerifier the way we have been until now can get a bit unwieldy, especially if each call needs to be configured in the same way.
For instance, if your team has decided to use
getClass-based equality checks instead of
instanceof-based checks, there will be a lot of repetition in your tests:
In such cases, you can use a configuration object to reduce the boilerplate:
ev object can now be reused freely.
This works for
.withGenericPrefabValues(), since these are not specific to the class under test.
Of course, you can still further configure each call: