Re^14: Do Pure Perl CPAN packages really need to use ExtUtils::Command::MM?

[ELISHEVA]

Well, that patch appears to have been made to the EVO module's test.pl - there is now a warning not to set test => {TESTS => ...}. Thank-you.

Sadly, it turns out that this solution isn't going to pass muster. The combination of test.pl + tests in "test" rather than "t" + no TESTS => 'test.pl' works under "make test", but it borks "./Build test". "./Build test" doesn't appear to be smart enough to give the test.pl file special treatment and it runs it through run_tests, resulting in the same problems with TAP that I was seeing earlier under MM: it goes to the console but not to Build.

I haven't given up experimenting with ways to get M:B to run test.pl as a harness rather than a test, but so far I haven't found a solution. Any ideas?

Re: what do I see.

With regard to t/*.t files, I see the same thing you do. I suspect that the t/ wasn't causing me a problem in my actual project directory because make/ExtUtils appears to only consider the immediate children of "t/". I name my tests after the class they are testing so all my tests are 2 or more levels deep.

If I set TESTS => 'test.pl', make/MM can't seem to find the TAP output though it is clearly displayed on the console (tested by inserting a fail() and diag()). However, the message I get is different from you. If only successful tests are run, I get "one test script could be run - FAILED before any test output arrived. FAILED alas no output ever seen." If I insert a fail(), the message is just the first and last sentence: "one test script could be run - FAILED alas no output ever seen."

[Anonymous Monk]

Any ideas?

Try the respective mailing lists