This is not a strictly Maven question. Hi Jake This sounds very interesting. I have two questions: 1. Is testing against an in-process database a better idea than using mock-objects to fake Connection, ResultSet, etc? (I need to test some hand-coded JDBC DAOs which I will redevelop later with Hibernate, but I can not throw them away just yet.)
2. Can you please tell me an example for dealing with SQL dialect differences. (I guess if you use Hibernate, this is taken care of with the dialect setting.) Janos This is why and how we use HSQL for testing. - It is much faster for developers who are in the habit of continuous testing to use HSQL instead of (for example) Oracle. - We don't have enough Oracle resources (connections, accounts, cpu) to support all the developers using it for continuous testing. - When running inside a debugger (like Eclipse or IntelliJ's), you can step down all the way into the database to see exactly what the sql is doing. - HSQL is only used for developer testing. Cruisecontrol and Maven and QA and everything else use both Oracle and SqlServer. - The driver, uri, username, and password are all in configuration files, so the same TestSetup is used for all databases. - The differences in the databases can be solved the same way as you would solve compatibility issues between Oracle and SqlServer. So developing against HSQL and going live against Oracle could have some issues, all problems should be found and fixed by always running against Oracle with infrastructure tools and in QA. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
