Pragmatic Unit Testing in Java with JUnit, 3rd Edition

Test Smell: Irrelevant Details in a Test

Your tests should execute cleanly, showing only a summary with the passing and failing tests. Don’t allow your test run to be littered with dozens or perhaps hundreds and more lines of log messages, “expected” exception stack traces, and System.out.println clutter.

Ensure test execution does not pollute console output.

When your test summary is clean, any new exceptions will stand out like a sore thumb rather than get lost in a sea of stack traces. You’ll also easily spot any new console output that you’ve temporarily added.

In the prior section, you split one larger test into two. Now, when you run ...