On 12/02/2003 9:04 AM, "Quinton McCombs" <[EMAIL PROTECTED]> wrote:
> I am trying to write some tests for both of these services. The problem > is that they require access to the database. > > I am going to be using mysql for the testing although any database will > work. For now, I am going to add mysql to the dependency list (well, > not now, but in a day or two when I am done). This is the only way that > I know to get the jdbc driver into the classpath during the unit > testing. Anyone else have a better idea on this? > > I also want to make sure that there are no objections to this idea... > This will complicate the build process requiring a database to be setup > first. > Quinton, I think it would be better to do something similar to what torque does - i.e. distinguish between the standard tests that are part of the build process (which should not require database access) and the runtime tests (that use the database via a profile). If you want to run the tests against the database then you need to explicitly invoke them using the runtime:test goal. Obviously this will allow builds to occur without the complication of having a database setup. Eric Pugh is doing some work in this area already, so you might want to touch bases with him as to where things stand with this. Cheers, Scott -- Scott Eade Backstage Technologies Pty. Ltd. http://www.backstagetech.com.au .Mac Chat/AIM: seade at mac dot com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
