Randy W. Sims wrote:
The following works fine under 'nmake test' as a 'test.pl' in the top
level folder:
-
if(1 == 1) {print "f1 ok\n"}
else {print "f1 not ok\n"}
if(2 == 2) {print "f2 ok\n"}
else {print "f2 not ok\n"}
It prints:
f1 ok
f2 ok
which
I'm just catching the tail end of this thread, so I hope I'm understanding.
On 02/26/04 03:11, Sisyphus wrote:
Randy Kobes wrote:
On Thu, 26 Feb 2004, Sisyphus wrote:
'perl -Mblib t\test1.t' works fine. But is it possible to get 'make
test' to automatically run that command (for each and every
Randy Kobes wrote:
On Thu, 26 Feb 2004, Sisyphus wrote:
'perl -Mblib t\test1.t' works fine. But is it possible to get 'make
test' to automatically run that command (for each and every '.t' file) ?
I've looked a little harder since making the original post.
Seems that if the tests are put in a 'tes
On Thu, 26 Feb 2004, Sisyphus wrote:
> Randy Kobes wrote:
> >
> > Hi Rob,
> > Does any further information result from running the
> > tests as
> > make test TEST_VERBOSE=1
> > or
> > perl -Mblib t/test1.t
> > etc. Can you post a sample that doesn't work?
> >
>
> Thanks Randy.
>
> Sett
Randy Kobes wrote:
Hi Rob,
Does any further information result from running the
tests as
make test TEST_VERBOSE=1
or
perl -Mblib t/test1.t
etc. Can you post a sample that doesn't work?
Thanks Randy.
Setting 'TEST_VERBOSE' does flush the output to the screen - but also
reports the s
On Wed, 25 Feb 2004, Sisyphus wrote:
> Hi,
>
> I have a module that I've written. The 'test.pl' script written for the
> purpose of running 'make test' was becoming a little large and unwieldy,
> so I broke it up into a number of test scripts, gave them all a '.t'
> extension and placed them in th
