OK, I'm trying to set up some tests and I'm just getting hammered on all
these little niggly points. So many of them that I have to assume I'm
doing something fundamentally wrong.
I used module-starter to kick start my little project and I now have
some files that are auto-generated for me.
~/foo/lib/Foo.pm
~/foo/t/00-load.t (and several others)
Cool. So I wrote up a couple of tests and tried them out.
With lots of errors... None of them were mine directly.
So I changed the command line to -I/home/tom/foo/lib/
and tried again. Cool. It worked.
So I tried to run all the tests at once using:
perl -T -I/home/tom/foo/lib t/*
and it runs only the first one found.... Ignoring the other 4 test scripts.
and prove is a little off as well. I have to run it from only the test
directory (foo/t/) or it will only see one test script.
I'm kind of frustrated at how really difficult this is becomming to set
up a test-centric development environment. Is it really supposed to be
this difficult?
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
