in reply to getting Test::More test names to print out

If you're going to be prompting the user, please use ExtUtils::MakeMaker's prompt function. It's a better idea not to prompt at all, but skip tests if certain %ENV variables aren't there, like DBI_DSN...

MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
** The third rule of perl club is a statement of fact: pod is sexy.

  • Comment on Re: getting Test::More test names to print out

Replies are listed 'Best First'.
Re: Re: getting Test::More test names to print out
by princepawn (Parson) on Jan 03, 2004 at 10:34 UTC
    prompt does not write to STDERR... it therefore prints nothing when used with make test.

    Carter's compass: I know I'm on the right track when by deleting something, I'm adding functionality
[reply]
[d/l]
[select]
      The reason you should use MakeMaker's prompt function is because it detects that it is not running interactively ... $default will be used without prompting. This prevents automated processes from blocking on user input.". Prompting from tests is just not a good idea, and prompting on STDERR is not a fix (just screws up automated testing).

      MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
      I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
      ** The third rule of perl club is a statement of fact: pod is sexy.

[reply]

In Section Seekers of Perl Wisdom