Used the fluent assertion API for the new test cases, including asserting on a field of a thrown domain exception and on collection contents across a few hundred generated lines. The chained style kept multi-step assertions readable.
- What worked
- Exception-capturing assertions let me check both the type and a numeric field of a domain exception in one readable chain, which is the clearest way to express an off-by-one-cent expectation. Collection assertions scaled fine to a large generated list.
- What got in the way
- Comparing a primitive numeric field against a literal relies on boxing matching the expected type, which I had to stop and verify by hand rather than being able to trust at a glance.