You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by epugh <ep...@upstate.com> on 2003/07/17 14:39:36 UTC
RE: cactus to test a turbine app
Slava,
You actually touched on a issue that bugs me with Cactus. I love Cactus,
but doing multipage tests from the perspective of the browser is relatively
cumbersome. However, Canoo tests are not nicely integrated into the
Cactus/Junit/Maven world of testing. So, here is what I am ruminating
about...
I am thinking of creating a Cactus testcase called CactusCanooTestCase that
allows you to run a canoo webtest script (just an ant script) from a Cactus
test. Now, I believe the test would actually end up running from inside the
container, but that shouldn't matter. Better though would be to run it from
the client.
At any rate, attached to the ant script would be a build listener that
interpreted any errors in the webtest script as a unit test failure, and
wrote it out to the junit .xml report file as such.
This would allow webtest to run inside the container, therefore allowing the
test to configure the environement, email servers etc...
However, where cactus does shine is testing your business objects. I would
definitly take the baby step approach, and check out some of the sourcecode
for Turbine's cactus tests in src/test-cactus. If you are interested, I
have my "TurbineTestCase" that handles creating the rundata and context
objects for me...
Good luck!
Eric
-----Original Message-----
From: slava@fft-geneva.com [mailto:slava@fft-geneva.com]
Sent: Thursday, July 17, 2003 11:13 AM
To: epugh@upstate.com
Subject: cactus to test a turbine app
Dear Eric.
my turbine webapp growing complexity brings me to take a dive in thorough
testing
I've peeked through the turbine pages, turbine-user mailing cactus lists to
see
that you are the person with most of posts using Cactus to test turbine
app.
the question which i have is whether it's possible to use cactus in testing
of
turbine webapp over several pages. e.g. to write a user interaction test
case.
Logging
going to chart
selecting items
pressing "buy"
logging out.
or you'd rather use canoo framework for this as you say in one of your
posts?
>>Then, using Canoo, I can test easily from a web browser perspective.
Has there been some integration work in cactus to test turbine webapps
easily ?
what's the short way to read how to use cactus ?
use it onver a simple servlet,
then try to run code snippets which you posted in wiki's turbine faq ?
kind regards.
slava zimine
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: cactus to test a turbine app
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
jbrekke@wi.rr.com (Jeffrey D. Brekke) writes:
Hi,
ah, this really sounds cool. I'll jot this down on my "blueskying for
the development environment" notes.
Regards
Henning
>Henning I agree with you and I think that any of the options I came up
>with should not be part of the Turbine build at all. They could be
>part of a development kit for *using* Turbine, ala a maven plugin to
>create and test a Turbine based application. I really don't see a
>need for anything more than cactus for Turbine itself at the moment.
>"Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
>> jbrekke@wi.rr.com (Jeffrey D. Brekke) writes:
>>
>>>epugh <ep...@upstate.com> writes:
>>
>>>Eric & Slava,
>>
>>>There is a webtest plugin for Maven in the sourceforge Maven Plugins
>>>project. We used to write straight junit based acceptance tests using
>>
>> Hi,
>>
>> while this is a cool thing, I really want to avoid some large "you
>> must get this plugin, this plugin and this plugin and that plugin from
>> CVS-HEAD" scenario to build the Turbine code. The fact that maven b10
>> seems to be able to build our site without any trickery, jar-copying
>> or stuff is very reassuring to me.
>>
>> If your plugin is available through some maven-ibiblio magic, then
>> cool, lets go ahead and test it. If a Turbine user must download it
>> from somewhere on the net, integrate it into maven so that he won't
>> get build errors, then I would veto its usage in the normal turbine
>> build process.
>>
>> If we want to attract users to Turbine, we must make it possible to
>> rebuild the code and work with the code without a large entry
>> barrier. I fully intend to add some sort of "build Turbine with
>> Eclipse cookbook", because using an IDE is a real option for many of
>> our users.
>>
>> Regards
>> Henning
>>
>> --
>> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
>> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>>
>> Java, perl, Solaris, Linux, xSP Consulting, Web Services
>> freelance consultant -- Jakarta Turbine Development -- hero for hire
>>
>> --- Quote of the week: "It is pointless to tell people anything when
>> you know that they won't process the message." --- Jonathan Revusky
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
>--
>=====================================================================
>Jeffrey D. Brekke jbrekke@wi.rr.com
>Wisconsin, USA brekke@apache.org
> ekkerbj@yahoo.com
>---------------------------------------------------------------------
>To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: turbine-user-help@jakarta.apache.org
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when
you know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: cactus to test a turbine app
Posted by "Jeffrey D. Brekke" <jb...@wi.rr.com>.
Henning I agree with you and I think that any of the options I came up
with should not be part of the Turbine build at all. They could be
part of a development kit for *using* Turbine, ala a maven plugin to
create and test a Turbine based application. I really don't see a
need for anything more than cactus for Turbine itself at the moment.
"Henning P. Schmiedehausen" <hp...@intermeta.de> writes:
> jbrekke@wi.rr.com (Jeffrey D. Brekke) writes:
>
>>epugh <ep...@upstate.com> writes:
>
>>Eric & Slava,
>
>>There is a webtest plugin for Maven in the sourceforge Maven Plugins
>>project. We used to write straight junit based acceptance tests using
>
> Hi,
>
> while this is a cool thing, I really want to avoid some large "you
> must get this plugin, this plugin and this plugin and that plugin from
> CVS-HEAD" scenario to build the Turbine code. The fact that maven b10
> seems to be able to build our site without any trickery, jar-copying
> or stuff is very reassuring to me.
>
> If your plugin is available through some maven-ibiblio magic, then
> cool, lets go ahead and test it. If a Turbine user must download it
> from somewhere on the net, integrate it into maven so that he won't
> get build errors, then I would veto its usage in the normal turbine
> build process.
>
> If we want to attract users to Turbine, we must make it possible to
> rebuild the code and work with the code without a large entry
> barrier. I fully intend to add some sort of "build Turbine with
> Eclipse cookbook", because using an IDE is a real option for many of
> our users.
>
> Regards
> Henning
>
> --
> Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
> hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
>
> Java, perl, Solaris, Linux, xSP Consulting, Web Services
> freelance consultant -- Jakarta Turbine Development -- hero for hire
>
> --- Quote of the week: "It is pointless to tell people anything when
> you know that they won't process the message." --- Jonathan Revusky
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
--
=====================================================================
Jeffrey D. Brekke jbrekke@wi.rr.com
Wisconsin, USA brekke@apache.org
ekkerbj@yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: cactus to test a turbine app
Posted by "Henning P. Schmiedehausen" <hp...@intermeta.de>.
jbrekke@wi.rr.com (Jeffrey D. Brekke) writes:
>epugh <ep...@upstate.com> writes:
>Eric & Slava,
>There is a webtest plugin for Maven in the sourceforge Maven Plugins
>project. We used to write straight junit based acceptance tests using
Hi,
while this is a cool thing, I really want to avoid some large "you
must get this plugin, this plugin and this plugin and that plugin from
CVS-HEAD" scenario to build the Turbine code. The fact that maven b10
seems to be able to build our site without any trickery, jar-copying
or stuff is very reassuring to me.
If your plugin is available through some maven-ibiblio magic, then
cool, lets go ahead and test it. If a Turbine user must download it
from somewhere on the net, integrate it into maven so that he won't
get build errors, then I would veto its usage in the normal turbine
build process.
If we want to attract users to Turbine, we must make it possible to
rebuild the code and work with the code without a large entry
barrier. I fully intend to add some sort of "build Turbine with
Eclipse cookbook", because using an IDE is a real option for many of
our users.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
hps@intermeta.de +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when
you know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
Re: cactus to test a turbine app
Posted by "Jeffrey D. Brekke" <jb...@wi.rr.com>.
epugh <ep...@upstate.com> writes:
Eric & Slava,
There is a webtest plugin for Maven in the sourceforge Maven Plugins
project. We used to write straight junit based acceptance tests using
httpunit to perform the types of tests described. Then I found
jWebUnit ( jwebunit.sf.net ), which is a nicer level above httpunit,
around the time I was looking into FIT and FitNesse ( fit.c2.com,
fitnesse.org ). The jWebUnit project has some FIT fixtures for
testing web applications through the user-interface ( i.e. like a
browser ) as you describe.
[ Short, incomplete description: FIT is a way for non-programmers to
define tests, basically in a table format. Then, saved as an html
table, it parses out the test and runs it, creating a html report by
coloring the cells of the table green or red ( failure ). FitNesse
takes this a step further, by using a Wiki to change/author and test
the pages on the fly. ]
So now we are using FitNesse for these types of tests using the
jWebFit fixtures. It works pretty well. I also started a fit plugin
for maven to just run the html files through fit, but FitNesse also
has a command-line for running test suites.
Hope this helps.
> Slava,
>
> You actually touched on a issue that bugs me with Cactus. I love Cactus,
> but doing multipage tests from the perspective of the browser is relatively
> cumbersome. However, Canoo tests are not nicely integrated into the
> Cactus/Junit/Maven world of testing. So, here is what I am ruminating
> about...
>
> I am thinking of creating a Cactus testcase called CactusCanooTestCase that
> allows you to run a canoo webtest script (just an ant script) from a Cactus
> test. Now, I believe the test would actually end up running from inside the
> container, but that shouldn't matter. Better though would be to run it from
> the client.
>
> At any rate, attached to the ant script would be a build listener that
> interpreted any errors in the webtest script as a unit test failure, and
> wrote it out to the junit .xml report file as such.
>
> This would allow webtest to run inside the container, therefore allowing the
> test to configure the environement, email servers etc...
>
> However, where cactus does shine is testing your business objects. I would
> definitly take the baby step approach, and check out some of the sourcecode
> for Turbine's cactus tests in src/test-cactus. If you are interested, I
> have my "TurbineTestCase" that handles creating the rundata and context
> objects for me...
>
> Good luck!
> Eric
>
> -----Original Message-----
> From: slava@fft-geneva.com [mailto:slava@fft-geneva.com]
> Sent: Thursday, July 17, 2003 11:13 AM
> To: epugh@upstate.com
> Subject: cactus to test a turbine app
>
>
>
> Dear Eric.
>
> my turbine webapp growing complexity brings me to take a dive in thorough
> testing
>
> I've peeked through the turbine pages, turbine-user mailing cactus lists to
> see
> that you are the person with most of posts using Cactus to test turbine
> app.
>
>
> the question which i have is whether it's possible to use cactus in testing
> of
> turbine webapp over several pages. e.g. to write a user interaction test
> case.
>
> Logging
> going to chart
> selecting items
> pressing "buy"
> logging out.
>
>
> or you'd rather use canoo framework for this as you say in one of your
> posts?
>
>>>Then, using Canoo, I can test easily from a web browser perspective.
>
>
> Has there been some integration work in cactus to test turbine webapps
> easily ?
>
>
> what's the short way to read how to use cactus ?
>
> use it onver a simple servlet,
> then try to run code snippets which you posted in wiki's turbine faq ?
>
>
>
> kind regards.
>
> slava zimine
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: turbine-user-help@jakarta.apache.org
--
=====================================================================
Jeffrey D. Brekke jbrekke@wi.rr.com
Wisconsin, USA brekke@apache.org
ekkerbj@yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org