On Sun, Feb 18, 2001 at 04:44:05AM +0000, Simon Cozens wrote:
> On Sat, Feb 17, 2001 at 09:46:31PM -0500, [EMAIL PROTECTED] wrote:
> > Why is t/TEST anything more than a thin wrapper around Test::Harness?
>
> Because of potential fragility. If Perl isn't entirely together when
> you're running the tests, the last thing you want to do is load up
> Test::Harness. t/TEST is (supposedly) crafted in such a way that it avoids
> using things that are likely to be broken.
Ok, can anyone remember or fathom what that certain way is? I have a
feeling that noble goal may have been patched into oblivion.
I'm not so worried about this anymore. It wasn't difficult to patch
up t/TEST to honor todo and skip tests, I'll be submitting a complete
patch shortly.
I'd still like to move t/TEST's guts into lib/Test/Harness/Basic.pm or
something. That way I can have POD and tests and all those nice
things and it will hopefully follow more of Test::Harness's changes.
