26 messages in org.apache.commons.devRe: [latka][anteater][jelly] possible...| From | Sent On | Attachments |
|---|---|---|
| Dmitri Plotnikov | Apr 24, 2002 7:06 am | |
| Scott Sanders | Apr 24, 2002 6:33 pm | |
| Ivelin Ivanov | Apr 24, 2002 7:20 pm | |
| Jeff Turner | Apr 24, 2002 10:23 pm | |
| Craig R. McClanahan | Apr 24, 2002 10:25 pm | |
| Juozas Baliuka | Apr 24, 2002 11:14 pm | |
| di...@multitask.com.au | Apr 25, 2002 12:26 am | |
| Ivelin Ivanov | May 15, 2002 8:26 pm | |
| Jeff Turner | May 15, 2002 10:57 pm | |
| James Strachan | May 16, 2002 12:38 am | |
| Ivelin Ivanov | May 16, 2002 6:29 am | |
| Morgan Delagrange | May 16, 2002 8:31 am | |
| Morgan Delagrange | May 16, 2002 8:41 am | |
| Ovidiu Predescu | May 16, 2002 10:38 am | |
| Jeff Turner | May 16, 2002 4:21 pm | |
| Ivelin Ivanov | May 17, 2002 11:09 am | |
| Morgan Delagrange | May 17, 2002 11:17 am | |
| Ovidiu Predescu | May 17, 2002 11:26 am | |
| Ovidiu Predescu | May 17, 2002 11:32 am | |
| James Strachan | Oct 30, 2002 4:16 am | |
| Vincent Massol | Oct 30, 2002 4:26 am | |
| Janek Bogucki | Oct 30, 2002 6:17 am | |
| James Strachan | Oct 30, 2002 7:33 am | |
| Morgan Delagrange | Oct 30, 2002 8:54 am | |
| Ovidiu Predescu | Oct 30, 2002 12:04 pm | |
| di...@multitask.com.au | Oct 30, 2002 3:47 pm |
| Subject: | Re: [latka][anteater][jelly] possible integration... (was Re: Latka & Anteater) | |
|---|---|---|
| From: | James Strachan (jame...@yahoo.co.uk) | |
| Date: | Oct 30, 2002 7:33:12 am | |
| List: | org.apache.commons.dev | |
From: "Vincent Massol" <vmas...@octo.com>
Cactus can use any JUnit test runner. Thus it should be able to use the exsiting JellyUnit tags with no problem. However, before running the tests there needs some preparations to make everything automatic: - packaging the application as a war or ear - configuring the container - starting it - deploying the app in it - stopping it
These could be easily achieved through a combination of Ant and Jelly tags, potentially used in a Cactus Tag library which would make the whole thing easier and more coherent to use?
Sounds good to me.
The war/ear would be generated by the build process I guess. Different tests may want to configure the container, start it, deploy app, stop it in multiple times. e.g. to test the same war or ear on different deployment configurations, containers or platforms. So deploying artifacts should be part of the test case; whereas the war or ear should be part of the build process shouldn't it?
James ------- http://radio.weblogs.com/0112098/
__________________________________________________ Do You Yahoo!? Everything you'll ever need on one web page from News and Sport to Email and Music Charts http://uk.my.yahoo.com