Bushwhacker to help team members debug unit test failures
24 Aug 2014
Reading time ~1 minute
Right now I'm working on a project with a few people who have never worked in Java before. There have been times where they'll experience some problem that they can't easily figure out. They send me the stack trace and instantly I know what the problem is. I wanted a simple way to automate this.
So I created Bushwhacker a simple library to help provide more helpful messages at development time. Senior members of the team edit and maintain a simple xml file that describes rules to detect particular exceptions and either replace or enhance the exception message in some way. The rules are fairly sophisticated -- allowing you to, for example, only detect IllegalArgumentException if it was throw from a stack frame from MyClassWhatever. Since the xml rules file is read off of the classpath, you can version the XML file along with your source code (in src/test/resources for example). And you can even maintain multiple rules files for different modules and compose them all together. So if there are common pitfalls in your corporate "commons" module you can keep the bushwhacker rules for it there, and put your team's additional rules in your module.