instancio VS Error Prone

Instancio for generating test data AssertJ Awaitility Quarkus FluentJdbc: a thin wrapper around jdbc, you can use it as an alternative for JPA and I use it in Quarkus

I've been experimenting a little and will be adding support for method references in the next release. Here's issue link if you want to follow.

Properly handling seeds and having reproducible objects was one of the main goals, so it should work as you'd expect. I'd suggest giving it a try and if you run into any issues, just post it on Github discussions.

error-prone is good for some extra static analysis.

A special kind of validation is enforcing that record fields are not null. (Un)fortunately, records do not have any special behavior regarding nullability. You can use tools like NullAway or Error Prone to prevent null in your code in general, or you can add checks to your records:

I am all in favour to more third side libraries adding functionalities, like Lombok, Manifold and error prone. As well as smaller projects like this shameless plug and what appears in this list

If only Google didn't suck when it came to Java9+ support... https://github.com/google/error-prone/issues/2649

I haven't used it. I use Google's ErrorProne + Lombok to prevent NPEs in java.

Take a look at NullAway, a plugin for Error Prone.

For some of this stuff, there are compiler extensions that allow extra type checking to be added e.g. Google Error-Prone: https://github.com/google/error-prone with stuff like: https://errorprone.info/bugpattern/ReturnMissingNullable.

Doesn't help you with third party libraries, but across an org applying that rule (and others!) typically ensures some consistency.

How to build a static analysis plugin. Google has a framework for Java with a good tutorial.