Please excuse the roughness of this module, but get feedback early is what
they say. For now, I've thrown it up at
http://2shortplanks.com/temp/tbt
And I'll let the start of the pod speak for itself:
NAME
Test::Builder::Tester - test testsuites that have been
built
speak for itself:
>
> NAME
>Test::Builder::Tester - test testsuites that have been
>built with Test::Builder
>
> SYNOPSIS
>use Test::Builder::Tester tests => 1;
>use Test::More;
>
>test_out("not ok
On Mon, 4 Feb 2002, Michael G Schwern wrote:
> Mark Fowler wrote:
> > 3. Um, licencing of borrowed code (see AUTHOR)
>
> Take whatever you like. In fact, if you don't mind, I'd like to
> distribute this with Test::Builder/More/Simple so I can use it to test
> all that.
Thanks. Yeah, distribut
H... I thought about the no_ending() problem and basically you
need to be able to access the internal list of test results and muck
with it to erase the results of the captured tests.
I'll put something in for that.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schw
ibute
it with Test::Builder then we don't need to do that (as we know they have
a capable T::B)
Speaking of that, I was wondering if you're going to distribute
Test::Builder::Tester with Test::Builder, then it might make more sense
that you take over maintenance of the module from tha
ave installed and frob the internal list if we can,
> otherwise just default to calling no_ending. Of course, if you distribute
> it with Test::Builder then we don't need to do that (as we know they have
> a capable T::B)
>
> Speaking of that, I was wondering if you're g
