Ovid wrote:
Last week I was at a testing conference with Acme and he came up with the idea
of installing tests. He looked into hacking Module::Build and
ExtUtils::MakeMaker. He also considered hacking CPAN.pm and CPANPLUS.pm.
While I don't know if he plans to continue working on this idea, he said he
didn't mind me posting his idea here for others to consider.
Basically, installing tests would be good because then you can run your full
test suite against *installed* modules. That would be nice because then you
could install a module and rerun your tests for your entire installation and
see what broke.
I love this idea, but here are some issues that we spotted:
1. How does one install tests for modules already installed?
2. If you install a module with already failing tests, you need to track what
the failures are so you can note different failures when you run the test suite
in the future.
3. What's the best way to install them? Should a separate tool just for this
be built?
Anyone want to take a crack at this?
I'm also going to post this to Perlmonks.
IIRC, I think this is something Ken has had in mind for a long time for
Module::Build. He might have some ideas about how it might be done.
Randy.
