Successful tests get their own markers
1.1.12 is available now. The biggest visible change is that successful tests now have a marker. I used the generic info marker so successes wouldn’t clutter up the Problems View. I don’t find the presentation attractive, but I was reminded of a quote from MythBusters, “Why bother to make it pretty if you don’t know if it’s going to work at all?” For that I’ll rely on you. Do you like having success markers?
Two other changes in this release:
- Max still does not parse all stack traces correctly. I received a couple of reports about this, but without the stack trace itself I couldn’t diagnose the problem. Now if Max has trouble with a stack it writes the stack to the error log. If you get one of these problems, please email me the contents of the error log.
- Malformed JUnit 3.8 test classes are now ignored.
February 16th, 2009 in
JUnit Max
I think I’d prefer a unique marker telling me that 500 tests out of 500 passed. If it was green, it would even be better! I find that lot’s of info markers in the problem view is very disturbing. This view satisfies me only when it’s empty!
I don’t like the success markers either — especially the ones in the source. Too much visual noise that I have to parse and then ignore.
If I want explicit positive feedback, I’ll run the Eclipse JUnit Runner via and wait for the green bar. I do that now sometimes, when I’m in a hurry and I know it will take Max a few seconds longer to catch up.
I agree with David that a quickly scannable single state indicator (perhaps in the status bar?) might be helpful. Something like a single icon that is red/yellow/green.