Tom Phoenix wrote:
On 7/2/06, Tom Allison <[EMAIL PROTECTED]> wrote:
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.
Perl's -T runtime switch doesn't mean "test"! :-) If you want to run
the full set of tests for a module, the usual way is 'make test'. (You
may need to run 'perl Makefile.PL' and 'make' first.)
Hope this helps!
--Tom Phoenix
Stonehenge Perl Training
I know about the '-T' being taint. But it's on by default after I ran
module-starter and since this is eventually going to be a web
application I have no intention of removing it.
I guess what I'm not clear on is I'm not trying to install this module.
I'm trying to write my own. I'm a long ways from installation at this
point.
I was trying to follow some of the ideas represented in "Perl Testing; A
Developer's Notebook" and "Perl Best Practices". Those ideas being:
start making modules with Module::Starter.
run prove -v t/*.t to check your tests.
the best I can get is prove -v ... decided that the pod-coverage.t test
cannot find the pod to evaluate. (any .pod, .pl, or .pm is considered a
POD candidate). All the others, including the pod.t managed to find the
appropriate file (lib/foo.pm).
I would have assumed that at this point I would be able to successfully
run all the tests (resulting many test failures because there's not much
there). But several of the test scripts just don't run or fail on
themselves (unable to do any real legitimate tests).
And so I'm really frustrated and not sure how it's all suppose to glue
together for me, "Joe Developer" who is trying to just write some
modules for my own personal use with the idea that some year I can
release something to CPAN. But some of these tools don't quite gel tonight.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
<http://learn.perl.org/> <http://learn.perl.org/first-response>
