On Fri, Jul 03, 2009 at 01:03:59PM -0700, Michael G Schwern wrote:
Dave Mitchell wrote:
So unless some other problem comes up, then 0.91 should match both those
goals and everyone's happy.
0.92 is on its way to CPAN with Craig's fixes.
http://github.com/schwern/test-more/tree/v0.92
Its
David Golden wrote:
On Sun, Jul 5, 2009 at 9:40 PM, Buddy Burdenbarefootco...@gmail.com 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/
Dave Mitchell wrote:
On Fri, Jul 03, 2009 at 01:03:59PM -0700, Michael G Schwern wrote:
Dave Mitchell wrote:
So unless some other problem comes up, then 0.91 should match both those
goals and everyone's happy.
0.92 is on its way to CPAN with Craig's fixes.
Hi Michael, et al,
Personally, unless I have a very complicated (and therefore unusual)
test setup, simply putting .pm files directly in t/ works just fine.
Then a simple use lib './t' does the trick. `prove`, `make test` and
even Test::Harness::run_tests(glob 't/*.t') ignore anything but .t
Shaun Fryer wrote:
Personally, unless I have a very complicated (and therefore unusual)
test setup, simply putting .pm files directly in t/ works just fine.
Then a simple use lib './t' does the trick. `prove`, `make test` and
even Test::Harness::run_tests(glob 't/*.t') ignore anything but .t
Michael G Schwern wrote:
Here it is much simpler, and going onto the front of @INC as it should.
use File::Spec;
BEGIN {
unshift @INC, map { File::Spec-rel2abs($_) } t/lib;
}
If I had to write all that code in every test I'd strangle myself.
Fortunately there's lib::abs which I'd
Greetings!
This email is to announce a new testing framework that I wrote (based
on Test::Builder), which I have tentatively called Test::Functional (as
in functional programming). Before finalizing it and uploading it to
CPAN and I figured I'd email you folks to get your thoughts on the
module
