While I applaud the effort to automate testing of new releases posted to CPAN, this is adding absolutely no vlaue in this case.
I am not looking forward to getting one of these for every platform someone decided to test this on.
This particular module can NOT be tested automatically, without some manual configuration. The tests can not automatically determine the configuration of your AFs infrastructure; you have to tell me.
Therefore, everytime I post this module, these tests are going to
fail. The same is going to be true for DBD::Sybase, or any of the
RDBMS modules which need to be configured with a data server, and/or
database name.
Is there a mechanism for telling the automated CPAN testing to skip this module? I do NOT want to hack the code to make the test skipped by default, because then unsuspecting administrators who install the module without reading my documentation will be give a false positive.
I would prefer to have the tests fail by default, but I don't want all these emails telling me something I already know.
Sounds like a job for META.yml. It would seem to be the best place to list things like:
Is the module specific to a certain platform(s)? Does testing require manual intervention? Does install require manual intervention? Does the module have external dependencies?
Randy.
--
A little learning is a dang'rous thing;
Drink deep, or taste not the Pierian spring;
There shallow draughts intoxicate the brain;
And drinking largely sobers us again.
- Alexander Pope