Hi Gary, I'm quite surprised by your memory issues: even in huge suites, it shouldn't use so much memory if correctly configured (for instance one of my clients has a suite with probably over 100000 steps now).
You can surely configure your project to use one "normal" output folder per subproject and then use custom glue code / xslt to present an high level overview. WebTest doesn't provide any facility for that (at least currently, but if you're welcome to contribute: a webapp to browse results is something I wait for since a long time ;-)). Cheers, Marc. -- Blog: http://mguillem.wordpress.com Gary Fay wrote: > Yes, this is a fairly sophisticated application, ColdFusion with CFC. > > We have 12 user categories. > There are 15 major functional areas > There is a sophisticated estimates and costing > There are ordering and approving modules > There are reporting and costing modules > ... more ... > > This project is probably 30 times bigger than my first (previous) canoo > test suite. > The smaller suite was having memory issues, so I am using subant and ant > build.xml in the subdirectories. > I am using the fileset, dirset to find and automatically run clean and > test targets in ALL subdirectories indescriminatly ... > > *My hope was that the subant tasks would help with memory (in addition > to increasing allowed memory with Environment variables.)* > - Keeping things in sync is a little painful - > > Each module has about 10 visible pages and 3-8 backing objects (CFC) (on > average). > > I have been using Canoo on an off where I could and like most projects > this complicated, stuff gets missed when testing (by hand). > > I did have some success with results in subdirectory and ANT move tasks. > > I built a summary module that read my runresults.xml file and manully > parsed the results to build a directory pass fail module. (counts passed > / counts failed) > Red background if count failed > 0, with links to the canoo report in > the subdirectories. > > (Directory tests like, "user type login and menu verification"; "Create, > Approve, Edit Products " ; "Create, Approve, Edit Catalogs"; "Create, > Approve, Edit Accounts " ... etc) > > When I moved from eclipse to CMD command lines my tests started failing > on invoke of the home page. At that point I got the latest version and > worked through the install > instructions > > > I discovered the runner, reasonably nice. I am making some use of the > sample app. > > Anyway, yes I am expecting hundreds of tests. > > > > --__--__-- > > Message: 5 > Date: Fri, 04 Jan 2008 10:21:44 +0100 > From: Marc Guillemot <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > To: [email protected] <mailto:[email protected]> > Subject: Re: [Webtest] How to set up reporting and subprojects > Reply-To: [email protected] <mailto:[email protected]> > Reply-To: Marc Guillemot <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> > > Hi, > > how many tests do you have (do you plan to have)? Unless this is a very > large number, I would rather use the facilities of webtest.xml and > generate a single report. > > Cheers, > Marc. > -- > Blog: http://mguillem.wordpress.com <http://mguillem.wordpress.com/> > > > Gary Fay wrote: >> Hello, >> >> I am trying to work with Webtest from Canoo, specifically I am trying to >> figure out the best way to organize and run tests AND get the reporting >> to match. (I am trying to figure out the best way to organize thing, and >> I hope the following isn't confusing. >> >> Basically I would like to know, should all reports go to one directory >> outside of the project (sub projects seem to get lost) or should the >> result be in each subproject and be copied or organized in some way >> after the test complete. >> >> (I am fairly light user of ANT and am still learning things about it. >> Setting up directory and filesets seems to be my biggest stumbling > block... >> ) >> >> It seems like the best way to do this is to divide the project up into >> subproject so that the directories look like the project >> >> for example >> -project >> -users >> -products >> -orders >> >> Would have test code set up like >> -projectTest >> -users >> -sub - build.xml >> -products >> -sub - build.xml >> -orders >> -sub - build.xml >> build.xml (project level file >> >> with build.xml set up in each subproject. >> >> I have the master build.xml file calling clean and test tasks in each >> subproject and was wondering about the reporting ... >> A hardcoded entry such as : >> c:\reports\project\report.xml seems to dump everything into the directory, >> >> it does seem to have a lengthy result.xml and lots of html files but the >> directory structure is not preserved ... >> >> I suppose the copy tasks could be used .... >> >> I wonder if leaving the results in each directory is better? >> >> ( I am not a big user of ant but I love Canoo's reports, I guess I am >> curious how best to set up the structures.) >> >> PS I noticed several years ago performance and maintenance seem easier >> when things are broken up and there is more than one big test script ...) >> >> ------------------------------------------------------------------------ >> Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try >> it now. >> > <http://us.rd.yahoo.com/evt=51733/*http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ >>> > > > > ------------------------------------------------------------------------ > Never miss a thing. Make Yahoo your homepage. > <http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs> _______________________________________________ WebTest mailing list [email protected] http://lists.canoo.com/mailman/listinfo/webtest
