That's one (of an ever extending list) of reasons that I dislike both the concept and implementation, and so do not use, the Test::* suite of modules.
Test code should not itself impose additional runtime constraints and requirements. If it does, then you end up having to write testcode to test the testcode as well as the testcode to test the code under test.
Testing is good. But in my opinion, and I realise that many (most?) will disagree with me, most of the mechanisms I've seen used for performing testing of Perl, and particularly those of the Test::* suite of modules I've looked at, are too invasive and impose too many constraints, requirements and dependancies.
That's not a well-formed or properly elaborated explaination. Maybe I'll get around to thinking it through properly and writing it up one day.
In reply to Re^6: When C<use Module;> *not* the same as C<require Module; import Module;>?
by BrowserUk
in thread When C<use Module;> *not* the same as C<require Module; import Module;>?
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |