Test::* failure?

BrowserUk has asked for the wisdom of the Perl Monks concerning the following question:

Could someone explain what this nonsense means?

C:\test\Win32-JobAdd>type t\Win32-JobAdd.t
# Before `make install' is performed this script should be runnable wi
+th
# `make test'. After `make install' it should work as `perl Win32-JobA
+dd.t'

#########################

# change 'tests => 1' to 'tests => last_test_to_print';

use Test::More tests => 1;
BEGIN { use_ok('Win32::JobAdd') };

#########################

# Insert your test code below, the Test::More module is use()ed here s
+o read
# its man page ( perldoc Test::More ) for help writing this test scrip
+t.


C:\test\Win32-JobAdd>perl t\Win32-JobAdd.t
1..1
Win32::JobAdd loadedok 1 - use Win32::JobAdd;

C:\test\Win32-JobAdd>nmake test

Microsoft (R) Program Maintenance Utility Version 9.00.21022.08
Copyright (C) Microsoft Corporation.  All rights reserved.

        C:\perl64\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_ha
+rness(0, 'blib\lib', 'blib\arch')" t/*.t
t/Win32-JobAdd.t .. Failed 1/1 subtests

Test Summary Report
-------------------
t/Win32-JobAdd.t (Wstat: 0 Tests: 0 Failed: 0)
  Parse errors: Bad plan.  You planned 1 tests but ran 0.
Files=1, Tests=0,  0 wallclock secs ( 0.03 usr +  0.05 sys =  0.08 CPU
+)
Result: FAIL
Failed 1/1 test programs. 0/0 subtests failed.
NMAKE : fatal error U1077: 'C:\perl64\bin\perl.exe' : return code '0xf
+f'
Stop.
[download]

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?

Comment on Test::* failure? Download Code

Replies are listed 'Best First'.
Re: Test::* failure? by syphilis (Archbishop) on Mar 19, 2012 at 06:49 UTC
Win32::JobAdd loadedok 1 - use Win32::JobAdd; I don't know where that `Win32::JobAdd loaded` is coming from, but it needs a newline at the end of it. I think it's the absence of the newline that's fooling test_harness() into thinking that no tests were run. Afterthought: I guess the `Win32::JobAdd loaded` must be coming from JobAdd.pm itself. Cheers, Rob	[reply] [d/l] [select]
Re^2: Test::* failure? by chromatic (Archbishop) on Mar 19, 2012 at 06:59 UTC
I think it's the absence of the newline that's fooling test_harness() into thinking that no tests were run. Very plausible. Any TAP consumer (such as Test::Harness) will only recognize `ok #` as a passing test.	[reply] [d/l]
Re^2: Test::* failure? by BrowserUk (Patriarch) on Mar 19, 2012 at 06:59 UTC
Nail - head - Contact. Thanks. With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. The start of some sanity?	[reply]
Re: Test::* failure? by Anonymous Monk on Mar 19, 2012 at 06:56 UTC
You probably you need to upgrade Test::More or the modules it uses `$ h2xs -AX -n Bunk Defaulting to backwards compatibility with perl 5.14.1 If you intend this module to be compatible with earlier perl versions, + please specify a minimum perl version with the -b option. Writing Bunk/lib/Bunk.pm Writing Bunk/Makefile.PL Writing Bunk/README Writing Bunk/t/Bunk.t Writing Bunk/Changes Writing Bunk/MANIFEST $ cd Bunk $ perl -Ilib t\Bunk.t 1..1 ok 1 - use Bunk;` [download]	[reply] [d/l]