really really hard to adapt it to work with Test::Builder unless you bit 
the bullet and used no_plan.  Template::Test just assumes it's in control 
of the testing process too much.

If I was to write a Template::Test2 module, how would people feel about 
this being distributed in the core for use of testing various things?  It 
would place another mandatory dependency on installing the software 
(though Test::Builder is core after 5.7.3.)

Likewise, being a good sort of chap I'd probably insist on testing 
Template::Test2 with Test::Builder::Tester too.  However, I wouldn't go as 
far as making that module mandatory - I'd just skip testing the testing 
module if we didn't have the testing module testing framework module 
installed (if you see what I mean ;-) )

Comments?  Suggestions?  Displays of apathy?

Mark.

-- 
s''  Mark Fowler                                     London.pm   Bath.pm
     http://www.twoshortplanks.com/              [EMAIL PROTECTED]
';use Term'Cap;$t=Tgetent Term'Cap{};print$t->Tputs(cl);for$w(split/  +/
){for(0..30){$|=print$t->Tgoto(cm,$_,$y)." $w";select$k,$k,$k,.03}$y+=2}



Reply via email to