Stas Bekman wrote:
Geoffrey Young wrote:
I never noticed it before, but 'make test' runs mod_perl core tests and ModPerl::Registry tests, but not Apache::Test tests. I kinda think we should be running all available tests, especially for software we're installing alongside mod_perl (even though it's a little backwards, testing Apache::Test _after_ we've used it to run the other tests :)
Do you really think we need that?
not really.
the two test suites that we are running are already testing the Apache::Test itself.
yeah, that's why I said it was kinda backwards.
In addition to having almost no tests in the Apache::Test suite. It seems to be just an unnecessary overhead, especially for threaded-mpm, which takes agest to start each new 'make test' and to finish it.
as it does on my pentium 120 dev box :)
I'd be all for it if Apache::Test was including tests unique to it.
So -0 here.
that's fine. the only situation where I would be more inclined to include them is if we could run them first, making it easier to isolate errors due to broken Apache::Test libraries rather then core mod_perl. but, as we both agree, running the tests is really overkill.
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
