I'm at a bit of a loss as to how to display results in end. any ideas?
I think ServletTestRunner already provides an output mechanism, but frankly I am not familiar with it.
I think it's a great idea and I'm happy to have you contributing.
Cheers, Nick On Jun 7, 2004, at 6:56 AM, Sumati Chaturvedi wrote:
Hi all,
Cactus doesn't have an Ant task for launching tests automatically using the ServletTestRunner. I think this could be interesting for various reasons :
- it can help us test functionally the ServletTestRunner. I don't think there is any way to do this right now .
- the configuration would be much simpler. There would be no classpath settings to be done on the client. Just a one time setting on the server would suffice.
- It provides a means for launching automatically tests using the ServletTestRunner.
- Any others?
- And finally, I'm relatively new to Cactus and I'd like to learn more about it while doing this!! :-))
I've discussed this a bit with Vincent, and I'd really like to know what
you think too
Following is one idea :
The <webrunner> task (I've called it this for want of other ideas) could
extend JUnitTask. It could reuse to a large extent the existing <cactus>
task except that it would first http-connect to the Servlet Test Runner.
From then on, the Servlet Test Runner can take over as it would for a
request coming from a browser. I'm at a bit of a loss as to how to
display results in end. any ideas?
What do you think?
I could work on this.
Regards,
Sumati
Nicholas Lesiecki Software Craftsman, specializing in J2EE, Agile Methods, and aspect-oriented programming
Books: * Mastering AspectJ: http://tinyurl.com/66vf * Java Tools for Extreme Programming: http://tinyurl.com/66vt
Articles on AspectJ: * http://tinyurl.com/66vu and http://tinyurl.com/66vv
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]