Hi all,
Anybody like testing and depend on PAR to work? If so, Module::ScanDeps
*badly* needs your help. There are currently only two tests, one of
which is conditional on Module::Pluggable, the other of which doesn't
provide much coverage.
What's the best way to test this sort of thing?
I could certainly run some simple checks on core modules, but I envision
myself quickly getting into difference between platforms and perl
versions.
It seems like the best way to get traction quickly is to throw some
real-world data at it and do some reasonable checks on the results.
e.g. we could easily generate a known set of required modules for each
module in the test set. However, the "who used what" data is currently
incorrect in a few cases, so a full expect test would break after a
bugfix or two.
So, where to get a good set of perl program data to test against?
Bundle a static set of modules with it? Create an optional "data pack"
to drive the testing?
I don't really want to write-up a bunch of Foo.pm and Bar.pm modules,
particularly since what we're dealing with is a rather large and
feature-packed system that's gone through quite a bit of fix-this-
here-and-that-there.
Suggestions? Volunteers?
Thanks,
Eric
--
Cult: A small, unpopular religion.
Religion: A large, popular cult.
-- Unknown
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
