or at least one failure) rather than void.

classes.
Took out optimization that says if two objects aren't the same class,
they can't be same().

(Why does this need to be hard-coded into the Tester at all?)

"objects of different classes can't be same()", I didn't notice that
some of the comparison code assumed both objects had already been
confirmed to be the same class.  As a result, comparing an object of a
class with no fields with one of a class with fields could either pass
or crash, depending on the order.
Fix: put back in the "if (sameClass)" test, but applying only to a
smaller section of code, so it's still possible to override this rule
with same().