One of my paranoid fears about
the junit assert testing is that it's impossible to tell if a test ran
and did everything, or didn't do anything. The output is the same in
both cases.

Dan.
It's a downside of assertion-based tests. My workaround is to seed the test with print statements, triggered only when a debug flag is set. When the silence scares me, I flip on the debug switch and listen to the reassuring chatter.

Reply via email to