On Thu, Sep 4, 2008 at 6:58 PM, Berg, Eric <[EMAIL PROTECTED]> wrote: > When I say that Test::Builder/Test::More/etc. are tightly coupled, I'm > talking really entwined. In some cases, we have created a class with a > bunch of test-related methods that look through the symbol table and > find methods that =~ m/^test_/ and then we run those tests, which > include calls to Test::Builder methods. There's no easy way to turn > this off.
This happens even when you're not testing? Or do you really want to run those tests every time anyone loads the module? > When you say that we could load it conditionally -- again, not really an > option -- are you thinking that we could do a conditional require() and > import explicitly or use fully-qualified calls? The former - a BEGIN block that determines the situation and loads test modules if you're not in mod_perl. You can also do tricks to fake Test::Builder's API without loading it, but that's a really roundabout way of dealing with the issue. - Perrin
