David,
> (3) either of the above but "use t::MyTest" rather than changing @INC
> with "use lib..."
>
> I don't think any one is much better than the others. I tend to like
> the "t::MyTest" approach from a readability standpoint because it's
> clear within the *.t file that this is a test library
On Sun, Jul 5, 2009 at 9:40 PM, Buddy Burden wrote:
> Let's say I have some common functions that I want available to all my
> .t files. So I've created a module that all the .t files can include.
> But where do I put it? I don't want to put it in lib/ because I
> don't want it to get installed,
Guys,
Let's say I have some common functions that I want available to all my
.t files. So I've created a module that all the .t files can include.
But where do I put it? I don't want to put it in lib/ because I
don't want it to get installed, right? But when I put it in t/, make
test can't see
Ovid wrote:
> I've altered Test::Builder to handle the cases where people are using the TB
> singleton at the top of their test files. You can get a copy at
> http://github.com/Ovid/test-more/tree/master if you want to test it.
I've merged it into schwern/master.
This is my first time maintainin
Hi all,
I've altered Test::Builder to handle the cases where people are using the TB
singleton at the top of their test files. You can get a copy at
http://github.com/Ovid/test-more/tree/master if you want to test it.
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/per
