On Fri, Feb 24, 2006 at 12:51:13PM -0800, Tyler MacDonald wrote: > > Sometimes it's beneficial for an automated tester to install > additional packages (in software I'm releasing, Test::CPANpm and > sqlite are perfect examples). It would be good to have a standard way > to tell a smoke tester what these packages are.
I had some thoughts surrounding this for a Bundle::CPAN::YACSmoke distribution, however, it also means that any distribution that doesn't include them in the PREREQ correctly will still get them by default, and may miss them in the FAIL report the author should get. Your suggestion seems reasonable, but currently CPAN::YACSmoke doesn't parse the META.yml file. In fact it doesn't parse any part of the distribution, just the name and the test results. It leaves all distribution parsing to CPANPLUS. It may be possible via a callback, but it seems more sensible to leave that in the hands of CPANPLUS. > If an optional_feature field for packages useful for automated > testing was standardized, functionality could be added to > CPAN::YACSmoke and PITA to take advantage of it, and then there would > be an easy way for an author to define prerequisites for doing an > exhaustive smoke test of their distribution. I think it would be possible for CPANPLUS to be patched to add these to the list of prerequisites if in AUTOMATED_TESTING mode, so it should be possible. I think PITA should be able to do something similar. Barbie
