introduction I’ve written a few integration test frameworks where the tests were written as JUnit @Test methods and defined via a fluent API that hid the plumbing from the test author. These were always executed against a mixture of locally installed & in-memory infrastructure. This worked well-enough in small development teams where the developers wrote the tests but wasn’t so good when I considered it for a larger project with a bigger team....
test your logging
I have yet to work on a project where we have attempted to test the log statements in the software & I’ve recently found myself asking why. Log statements added by different developers (sometimes guided by a woolly statement on logging in the project coding guidelines) vary in their number, style & usefulness. Logging ends up inconsistent in its level of detail, format & log level. The logging of the same event could end up like any of the following:...