Michael G Schwern wrote:
The solution is to use the no_chdir flag to File::Find::find() so that your
tests are run from the top level of your source directory, not inside t/.
Many thanks, Michael. Your suggestion was spot on. Not only do I no
longer get the error message, the POD tests are
Michael G Schwern wrote:
That's an error from Test::Builder (ie. the thing behind Test::More and
others) and not Test::Harness. Its coming from the test program your
harness is running, not from the harness itself.
[snip]
Thanks, Michael. I'll try that.
Regards,
Troy
On 12/19/05, Troy Denkinger <[EMAIL PROTECTED]> wrote:
> The error is related to my pod.t which is, just as in the docs:
>
> use Test::More;
> eval "use Test::Pod 1.14";
> plan skip_all => "Test::Pod 1.14 required for testing POD" if $@;
> all_pod_files_ok();
>
> Running this under my test harness
On 12/15/05, Troy Denkinger <[EMAIL PROTECTED]> wrote:
>
>
> I wrote a test harness - you'll find the code below my signature, if
> you're interested. When I run it, I get the following:
>
> You said to run 0 tests! You've got to run something.
> # Looks like your test died before it could output
Ian Langworth wrote:
No one else has replied, so here's a shot in the dark: Try setting the
PERLIO environment variable to "crlf" (without quotes).
Thanks, Ian. That didn't rid me of the error, but I did do a bit more
digging. The error is related to my pod.t which is, just as in the docs
No one else has replied, so here's a shot in the dark: Try setting the
PERLIO environment variable to "crlf" (without quotes).
--
Ian Langworth
