epugh <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Thursday, July 17, 2003 11:13 AM > To: [EMAIL PROTECTED] > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- ===================================================================== Jeffrey D. Brekke [EMAIL PROTECTED] Wisconsin, USA [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
