On Sat, Aug 25, 2001 at 02:56:30PM +0100, Tony Bowden wrote:
> > Everything in lib/.  For t/ you'll have to use your judgement.  I
> > added some stuff about this into perlhack.pod in bleadperl (attached).
> 
> I'm not sure I have enough judgement for this yet! :)
> 
> I'm currently adding stuff to t/op/universal.t

Test::More depends on UNIVERSAL::isa if you're going to use any of the
eq_* functions.

Actually, t/op/universal.t is pretty sensible as it stands.  It's got
a test function.  If it's got that, it's pretty flexible as it stands.

Go after something like... t/op/sub_lval.t or t/op/readdir.t.  Things
that are still doing:

    print "# `$out'\nnot " unless ref $out eq 'main'; # Not reached if error.
    print "ok 1\n";


> Perhaps those with enough judgement could put together a guide to where
> it would be acceptable to use Test::More in the code?

With anything outside the lib/ tests it's pretty much case-by-case.
I can tell you which ones are right out:

    t/base, t/cmd, t/comp

You can probably safely get away with using Test::More in:

    t/io, t/pod

t/op and t/run... those are tricky.  Ask first.


-- 

Michael G. Schwern   <[EMAIL PROTECTED]>    http://www.pobox.com/~schwern/
Perl6 Quality Assurance     <[EMAIL PROTECTED]>       Kwalitee Is Job One
If you have to shoot, shoot!  Don't talk.
                -- Tuco, "The Good, The Bad And The Ugly"

Reply via email to