On Feb 9, 2004, at 6:20 PM, Stas Bekman wrote:
- As the number of tests grows it takes longer to start the test
suite. Under threaded mpms it can take a very long time on a loaded
machine (10 minutes and more). At the moment we keep on bumping up the
I've noticed this on lots of CPAN modules other than mod_perl. It seems to me that there should be two test suites for most complex modules: developer tests and installer tests. The developer tests would check every corner case of every complex function -- like a full regression test might do. The installer tests would check for the basic functionality to see if the thing is installed properly, and perhaps test some things that may be system-dependent, and be a subset of the developer's tests.
For sure, mod_perl could do with a split like this.
We have no developer vs. installer separation. All tests are equally important and could detect bugs or environment differences. If we split the tests, we will still have users run them all (minus the special experimental tests that we have discussed earlier).
The problem that we are trying to solve is the growing startup time, not the amount of tests being run (which will probably double in size with time).
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
