David Wheeler wrote: > Hi All, > > A big debate is raging on the Bricolage development list WRT CVS > configuration and application testing. > > >http://www.geocrawler.com/mail/thread.php3?subject=%5BBricolage-Devel%5D+More+on+Releases&list=15308 > > It leads me to a question about testing. Bricolage is a monster > application, and its UI is built entirely in HTML::Mason running on > Apache. Now, while we can and will do a lot more to improve the testing > of our Perl modules, we can't really figure out a way to automate the > testing of the UI. I'm aware of the the performance testing utilities > mentioned in the mod_perl guide -- > > http://perl.apache.org/guide/performance.html > > -- but they don't seem to be suited to testing applications. > > Is anyone familiar with how to go about setting up a test suite for a > web UI -- without spending an arm and a leg? (Remember, Bricolage is an > OSS effort!).
You probably also need some good back-end engine for testing since you mostly likely need to test against a live Apache/mod_perl. If that's the case you should try to use the new Apache::Test framework that will be released with mod_perl 2.0. You can get it from here: http://cvs.apache.org/snapshots/modperl-2.0/ (or use cvs) Some docs are here: http://cvs.apache.org/viewcvs.cgi/modperl-docs/src/docs/2.0/devel/testing/testing.pod _____________________________________________________________________ Stas Bekman JAm_pH -- Just Another mod_perl Hacker http://stason.org/ mod_perl Guide http://perl.apache.org/guide mailto:[EMAIL PROTECTED] http://ticketmaster.com http://apacheweek.com http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
