I care because I "write a little, test a little". I don't want to wait to build a war every time I write a test and want to run it. So in my desktop/ development environment, I deploy an "exploded" war (WebLogic 6.1).
I set WebLogic to dynamically reload classes when they change (after I write the next test) so I just refresh browser, set to the ServletTestRunner URL, to see the results of the next test. In production, yes, we deploy a real war, which we do not test with Cactus. I will look into <runservertests>, thanks. By the way I really like Cactus. Thanks --DP -----Original Message----- From: Vincent Massol [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 16, 2004 11:00 AM To: 'Cactus Users List' Subject: RE: ServletTestRunner ant usage help > -----Original Message----- > From: David Plass [mailto:[EMAIL PROTECTED] > Sent: 16 March 2004 15:28 > To: Cactus Users List > Subject: RE: ServletTestRunner ant usage help > > But <cactus> only works for war or ear files, right? Not exploded wars? Why do you care? Your application will be deployed as a war right? So you already have some goals that create this war. You simply need to cactify this war (cactifywar) and then use <cactus> for it to be deployed. Now if you with to perform hot deployments of exploded wars, you can use the <runservertests> task. Would that work for you? Thanks -Vincent > > Thanks > --DP > > > -----Original Message----- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, March 15, 2004 5:28 PM > To: 'Cactus Users List' > Subject: RE: ServletTestRunner ant usage help > > > Hi Steven, > > > -----Original Message----- > > From: Ger, Steven M. [mailto:[EMAIL PROTECTED] > > Sent: 15 March 2004 23:09 > > To: '[EMAIL PROTECTED]' > > Subject: ServletTestRunner ant usage help > > > > Hey all, > > > > I've been using the cactus browser interface (i.e., > > http://localhost:7001/myapp/ServletTestRunner?suite=MyTest&xsl=cactus- > > report > > .xsl) to execute in container tests. All tests are written to support > > this > > interface. I'm trying to automate this with CruiseControl. I'm > looking > > for > > an ant task that will execute the previously mentioned URL and report > on > > the > > results. I've notice JUnitEE has a task such as this: > > > > <target name="do-run-tests"> > > <junitee url="http://your.server:port/myTest/TestServlet"; > > printsummary="true"> > > <test runall="true"/> > > </junitee> > > </target> > > > > Does cactus have anything like this? If not can anyone recommend a > > different approach. > > The solution with Cactus is to use the <cactus> Ant task. Please see > http://jakarta.apache.org/cactus/integration/ant/index.html. It provides > even more than the <junitee> task as it can also perform application > deployment/start/stop of containers. > > You can also check the Servlet sample which is part of Cactus > distribution to see it in action. > > Thanks > -Vincent > > > --------------------------------------------------------------------- > 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] --------------------------------------------------------------------- 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]
