I'm not sure why replacing that with "make plan; make test" (or perhaps just "make plan test") is such a hardship for you.
It's a hardship because I'll forget to do it. My fingers know how to type 'make test' all by themselves; they don't even ask my spinal column for guidence.
But it sounds like to don't care at all about the types of failures that plans are meant to catch
That's almost true. I certainly don't care enough to maintain a magic number at the top of all my test files. But I do care enough to bang out a module that I can add once and forget about. It sounds like some combination of a source filter and fork() will do the trick, so I think I'll give that a try.
-sam
In reply to Re^4: How can I write Test::Finished? (auto count)
by samtregar
in thread How can I write Test::Finished?
by samtregar
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |