So now you've got to invent names for all your tests. Just so you can search for that name to find the test?
No; read the documentation, or at least the output tobyink posted.
... which could be Autoloaded...
And if I use Carp::cluck or Carp::confess...
And if I need to pause the test at some point -- for example, so that I can attach a (C-level) debugger -- I can just stick a <STDIN> in there.
All of those things are possible with Test::Builder and friends too, without you having to edit your test files when you want to debug them. Sorry, "if" you want to debug them.
It doesn't force-fit me into a single one-size-fits-all methodology...
Repeating that ad nauseum doesn't make it true.
In reply to Re^8: Developing a module, how do you do it ?
by chromatic
in thread Developing a module, how do you do it ?
by mascip
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |