We have similar idea. There is only one project CVS. We checked it out into 3 sandboxes, for 3 levels of tests ( be length of testing: unit, acceptance-short, acceptance-long), then configure project.xml file in each sandbox to include or exclude certain tests.
The cruisecontrol is setup in different intervals to drive these 3 sandboxes. -- Andrew Chen Principal Engineer Engineering Computing Nuclear Fuel Westinghouse Electric Company 1-412-374-2316 -----Original Message----- From: Gimbel, Trevor [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 07, 2005 1:50 PM To: Maven Users List Subject: RE: SmokeTests in Maven For our application, we have a separate project in CVS and maven (ui-test), that is used to build and execute our integration tests. This approach allows us to run the tests on an as needed basis, since they do take longer than straight JUnit tests. -----Original Message----- From: Akins, Greg [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 07, 2005 1:05 PM To: Maven Users List Subject: SmokeTests in Maven I would like to write some smoke tests against a deployed web application. Seems like I should be able to run Canoo tests after completing a tomcat:deploy. Can someone advise the easiest/best way to do this? I had thought about wrapping some ant/jelly in a postGoal; but thought there might be a better way? Greg Akins Software Engineer Sony Electronics, STP Systems 724.696.7322 (Sony) 724.696.6147 (AV) 724.454.7790 (Cell) 412.590.3973 (Pager) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
