in reply to No plan "weakens" my Test scripts?

I find Test::More qw(no_plan); incredibly convenient whilst I am developing the module and tests in question, but once I can say "Finished", then put in the number of tests. This way you get the ease of not having to annoyingly update the test number, but get the protect once your done.

...it is better to be approximately right than precisely wrong. - Warren Buffet

Replies are listed 'Best First'.
Re^2: No plan "weakens" my Test scripts?
by spurperl (Priest) on Feb 08, 2005 at 11:13 UTC
    This is a generally good approach, applicable to many tasks we programmers do. A "stub" for development that makes it easier and can be later removed when the system is released.

    It's important not to forget to remove the stub though !

[reply]
Re^2: No plan "weakens" my Test scripts?
by dragonchild (Archbishop) on Feb 08, 2005 at 14:43 UTC
    Actually, since I want to write my tests in an intentive manner, I never use no_plan. I want to be completely aware of how many tests I'm adding, because each set of tests should be testing a very specific scenario I have in mind. Otherwise, I'm not doing any better than slinging tests around. (This is equivalent to slinging code around.)

    Being right, does not endow the right to be rude; politeness costs nothing.
    Being unknowing, is not the same as being stupid.
    Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
    Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

[reply]

In Section Seekers of Perl Wisdom