Up to beta-4 Maven used to have an integration unit test target to run cactus based programmer integration tests. Post beta-4 a plugin for cactus is needed and I don't believe any work has been done on this. I don't have a solution but here's the breakdown we have, these are currently all junit tests:
programmer tests ( fast "unit" type tests ), programmer integration tests ( slow "unit" type tests that may depend on external systems like a database ) customer tests ( acceptance/funtional, black box type tests, think httpunit, requires installed application ) The programmer tests most likely are the plain unit tests that maven runs during the build. It would be interesting if there could be another include/exclude for the iu tests. I don't think they need to be separated from the unit test code/class directory, just selected from the pool of tests to run? ================================================================= Jeffrey D. Brekke Quad/Graphics [EMAIL PROTECTED] http://www.qg.com > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 27, 2002 10:01 AM > To: [EMAIL PROTECTED] > Subject: How to run Integration Unit Tests > > > I solved my logging issues, it turns out I needed in a > basetestcase to init > the log4j system. ARgh.. Now I am trying to figure out how best to > structure my Integration Unit Tests. > > Does the maven test target run IU tests? I checked out > Turbine 2 from CVS > and ran the target test, then the site target. However, the > various IU > tests are not listed, in fact apparently there are no Unit > tests at all! > > So how should I run my IU tests? I don't want to run them constantly > because some can take up to 5 minutes of processing to do. > > Eric > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
