[Webtest] WebTest combineded with Cactus?
Mon, 21 Jul 2003 07:41:24 -0700 (PDT)
I dont know if I am on the write track but we have a
simialr system running with Gump (from Apache), Maven,
And I guess you could do the same with it too...
--- EPugh@upstate.com wrote:
> Wow! Very succinct! I wish I could have written my
> original email like
> Yes, I want to be able to postprocess the results
> from the WebTests, and I
> want to be able to 1) build my code, 2) start up my
> server, 3) Run my
> Webtest script, 4) collate the results with out
> resorting to lots of
> ant/jelly trickery.
> I have found that the more configuration required,
> the less likely the tests
> are maintained. Additionally, if Cactus ran the
> webtest script, then
> presumably when my Continous Integration package
> like CruiseControl or
> Anthill was run, it would run the webtests scripts
> without even noticing!
> Eric Pugh
> -----Original Message-----
> From: Scot Hale
> To: firstname.lastname@example.org
> Sent: 7/18/03 6:03 PM
> Subject: Re: [Webtest] WebTest combineded with
> I agree with you Eric. It is difficult to maintain
> the web-tests with
> dynamic/changing/growing applications, but I haven't
> used Cactus.
> Are you just looking for a more generic interface to
> the Canoo webtest
> One that would be able to start a test(s) which are
> defined in ant.xml
> files and gather the results in via a java
> object, (or xml?) of some
> 1.) Cactus Starts
> 2.) Cactus Calls Canoo Interface (any number of
> 3.) Canoo interface starts Ant
> 4.) Canoo interface gathers results from the test
> and returns them
> 5.) Catctus does what ever it needs to with the
> I am guessing the only thing that is currently
> missing is a nice
> interface, and perhaps a Cactus friendly object to
> Is that anything like what you are looking for Eric?
> ----- Original Message -----
> From: EPugh@upstate.com
> To: email@example.com
> Sent: Friday, July 18, 2003 4:46 AM
> Subject: [Webtest] WebTest combineded with Cactus?
> Hi all,
> I want to throw out this idea and see what people
> The Problem:
> I used to use WebTest extensively to test my sites,
> but the cost of
> maintaining the scripts, and running them by hand
> become to much work.
> I started using Cactus to test my business objects,
> and that worked
> well. I then started to test my webapps using
> Cactus to simulate a
> browser. This would work okay for one page, but if
> you wanted to test a
> couple of pages (a la WebTest) it became a maintence
> nightmare. What
> was great about WebTest was that the scripts are
> easy to run. What is
> hard is that they aren't integrated with the rest of
> build->test->continous integration regime using
> junit and cactus.
> What I Want:
> Use Webtest from inside Cactus to test my webapps
> from a browser
> I noticed that Sigi's webtest plugin is able to
> format the webtest
> output in something that looks very close to a junit
> style report. It
> seems to me that similar to the way that Ant runs
> testcases that
> execercise various build.xml test files, I could
> have a
> CactusWebTestTestCase that would run in container
> the webtest scripts.
> The errors etc coming from WebTest could be treated
> as Junit style
> assert's and then be formatted using the standard
> cactus tools... Which
> means that when, in Maven, I click on
> cactus-reports, the results of my
> webtest scripts will be there!
> The other reason to use Cactus, instead of the maven
> webtest plugin is
> that using Cactus I can configure my environment
> before running the
> scripts to have everything I need. Preset the
> database, generate any
> files, etc.. And the script can just reference
THE FOUR STAGES OF LIFE:
1) You believe in Santa Claus.
2) You don't believe in Santa Claus.
3) You are Santa Claus.
4) You look like Santa Claus.
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!