I remember something like this as well but I also seem to remember that there was something "wrong" with it. If I'm not mistaken, it just throws the whole SQL script into one big JUnit fixture and then even if the work is greatly reduced, there's still an awful lot of work that has to be done manually.
Personally I find that running the SQL file against the output file within a JUnit test is acceptable.. the test functionality is maintained and the test is converted into JUnit, so I'm not sure there are any significant drawbacks about it. Tiago On Sat, Feb 12, 2011 at 5:11 PM, Bryan Pendleton <[email protected] > wrote: > \> As you'll be able to see on that > > page, SQL tests can be converted by either running the current SQL file as >> part of a test that extends from the >> util.ScriptTestCase or... alternatively... you can convert the test by >> hand with JDBC calls that execute the SQL commands. >> > > Isn't there still a tool that performs the conversion > from SQL script to JDBC test case automatically? You > still have to process the results by hand, but I recall > that the tool does an enormous amount of the heavy lifting > for you. > > I think it's called: > > org.apache.derbyTesting.functionTests.util.SQLToJUnit > > thanks, > > bryan >
