My main comment would be that it can be very easy to get seduced in to
dependency bloat when writing Test:: modules, and you should pay extra
attention to avoiding it if possible.
This is especially so if you have a dependency on a Module::Build Test::
modules, which is going to want to install Module::Build for people that
don't have it yet.
It's especially grating when someone's module fails because it got stuck
somewhere down in a cascade of Test:: dependencies. Same level of
problem, but as the Mozilla people would say a "highly visible" problem.
Adam K
Ovid wrote:
Hi all,
For all of my harping about testing, I've never actually written a test
module (though I've submitted patches). I just uploaded my first
module, Test::JSON. (JSON is "JavaScript Object Notation",
http://www.crockford.com/JSON/).
As it's not hit the CPAN yet, I've attached a copy. Feedback welcome.
Internally it uses the following:
'JSON' => 1.00,
'Test::Differences' => 0.47,
'Test::Simple' => 0.62,
'Test::Tester' => 0.103,
Cheers,
Ovid
