Fewer redundant errors (and almost a cool view)

1.1.21 is available now. The visible change is that more compilation errors are discarded instead of being redundantly reported by Max. I had requests to stop Max entirely while there were compile errors, but I actually like to have the feedback from all the tests that can run, even if some are blocked from running by errors. Let me know what you think.

I probably shouldn’t write these posts when I’m frustrated, so I’ll be brief with the rest of this. I ran into a strange problem with Eclipse where it won’t install the icons for the Max plugin. It could be pilot error, but I wasted a whole day tracking it down, a day I could have been implementing new functionality. Hence my frustration.

If you don’t mind using a view with ugly default icons, check out out Windows>>Show View…>>Other…>>JUnit Max>>JUnit Max. The view is a tag cloud derived from the words used in the names of the tests in the selected project. It packs a lot of information in a small space. I hope to use it as the vehicle for test run feedback and navigation (the long-requested stack trace navigator). I’m eager for feedback about the general idea. Does this give you valuable information about your tests?