Why does Integer identity comparison work for small fixtures but fail for larger values?

Two wrapper variables are object references. A test that happens to receive reused wrapper objects can conceal an identity comparison. For two optional invoice counts, use Objects.equals(left, right) with java.util.Objects imported. For required arithmetic values, validate presence and compare primitive ints. Do not adjust the wrapper cache or pick a magic numeric boundary as a correctness fix. A cache setting belongs to runtime behavior, not to the equality rule of your domain. Build fixtures with equal numeric values created through different paths, unequal values and nulls. Check that equality remains symmetric. Objects.equals compares the wrappers according to their own types: an Integer and a Long are not automatically equal simply because their printed digits match.