We have explored the possibility of adding JUnit tests. The main problem is defining meaningful tests that do not require knowledge of what data to use for paramters to finders and what results are expected.However, we'd love to hear more about this idea. Can you provide an example of the type of unit test you would like to see generated?
I see your point regarding requiring knowledge of parameters etc for tests. If Firestorm could generate the test classes and methods per DAO this might encourage developers to fill-in-the-blanks with data specific to their database and needs. I ended up writing my own tests per table but found they needed to be run in a particular order to be useful. My idea was that the tests could run and leave the database in a consistent state yet satisfy my test conditions. e.g.
-INSERT test Customer,
-run a query or queries based on inserted test Customer,
-UPDATE the test Customer,
-run a query or queries based on updated test Customer,
-DELETE the test Customer,
-run a query or queries to confirm test Customer deleted
Another thing which might be useful for rapid prototyping without having to actually setup any database is to somehow mock a DAO implementation, say using XML files and XMLQuery and a limit of 10 records per table. In theory, a developer could then code and test a system against a lean mock database before choosing a real database with real data.
Also, Firestorm gives you the ability to create custom accessors such as getThis() and getThat() but what about custom modifiers such as updateThisWhereXXX() and deleteThatWhenXXX(). Will this be supported in the future?