FWIW, there are cactus tests of the scheduler service donated when some patches came
from jetspeed and I think you could use cactus for tests that will depend on external
systems. That said, what are you testing that needs the database? Aren't you just
testing torque then? Is there some way we can test the service logic without
requiring a database ( I'm not sure, just asking outloud )?
"Quinton McCombs" <[EMAIL PROTECTED]> writes:
> 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.
--
=====================================================================
Jeffrey D. Brekke [EMAIL PROTECTED]
Wisconsin, USA [EMAIL PROTECTED]
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
