Unit testing can be hairy. It requires knowledge of the existing codebase as well as knowledge of various testing domains (unit test tool, mocking tool for db / file system interaction / servlet interaction, test environment setup tooling). These issues do not even begin touch the actual validity and usefulness of the unit test itself. I’ve successfully used junitfactory.com to generate JUnit tests for my NONCONFIDENTIAL java classes. Its a real smart tool and even calls the private methods of my classes via java reflection, a mechanism by which to learn about the class through metadata in the form of functions, fields, constructors, etc. It also has a mocking technology; its just that this seems like a handholding process if one wants to generate meaningful tests. Overall, pretty solid tool and I guess the development version is integrated with cruisecontrol – I just don’t have that kind of money to invest…yet.