Re: Unable to get terminal size


Perl-Sensitive Sunglasses
	PerlMonks

Re: Unable to get terminal size

by danmcb (Monk)

on Sep 20, 2007 at 08:40 UTC ( [id://640068]=note: print w/replies, xml )

Need Help??

in reply to Unable to get terminal size

I am in the habit of doing :

perl -Ilib t/mytests.t
[download]

and adding the -d switch to this is fine. I've never yet seen a case where this passes but "make test" fails - if such things do exist, wouldn't a better approach be to fix that - if possible?

To be honest, I've not yet seen a benefit to doing "prove" in place of this. Which doesn't mean that there aren't any, of course ...

Comment on Re: Unable to get terminal size Download Code

Replies are listed 'Best First'.

Re^2: Unable to get terminal size
by Ovid (Cardinal) on Sep 21, 2007 at 10:45 UTC

prove has many benefits that people don't always appreciate. It's easy to do recursive tests, shuffle tests, run all tests in a particular directory, etc. However, with Test::Harness 3.0, you get much more. You can:

Switch in your own test harness
Have greater control over what you do and do not see (quiet output, only failures, etc.)
Get colored test output
Run tests in parallel
Create TAP archives
... or any other custom test behavior you need.

In short, the current prove is useful, the upcoming version is even more useful.

As for adding the -d switch, that becomes very handy when you think there might be a problem with test/code interaction (ever seen code fail in the test suite but not when run directly?).

Cheers,
Ovid

New address of my CGI Course.

[reply]

In Section Seekers of Perl Wisdom