NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
drhyde (1683)
Monday October 06, 2003
01:23 PM
Tests
I have a few Acme modules. Every so often, someone will join the CPAN testers, go through them, and I'll get a whiny email about Acme::Pony not having any tests.
Yes. I know it hasn't got any tests. I don't care that it doesn't have tests. If you want robust code that you can use in your mission-critical life-support bet-the-company application, stay the hell out of Acme::*.
Now I'm quite happy to receive reports that tests have failed - that's useful. But please please please can people stop telling me that I didn't bother writing any tests at all!
And if *you* care about Acme modules not having tests - patches welcome.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Or is it a BUG?"
"Let's call it an accidental feature. :-)"
--Larry Wall in <6909@jpl-devvax.JPL.NASA.GOV>
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Partial Agreement (Score:1)
Sometimes, the tests are the point. Take, for example, Acme::Incorporated [cpan.org]. How would you test something like that?
RT Ticket for no Changes file (Score:2)
Casey West
Yarrr! (Score:1)