vtest is a verbose wrapper for JUnit.
As someone who uses TDD in my day job, I often do my main development entirely with unit tests. I will then run the end to end user test only after the feature is mostly complete and I'm testing the integration of various components by hand. In these cases, knowing what an incorrect value is, or even what a correct value is (if say non null is required), piggybacks with good old school console debug spam style development.
vtest is currently very young, being pulled from the utils package of my artificial life simulation package. After pushing this to a more feature complete status, I'll try to deploy this to an artifact repo. In the meantime, if you want to use this code, I've included a sample usage below:
import com.johnuckele.vtest.Tester;
...
int basicMath = 2 + 2;
Tester.test("Addition test", basicMath, 4);
vtest doesn't specify a strict 'expected' vs 'actual' ordering, since most of the tests are equality or inequality tests, and one could argue either format is more readable.