If you're talking about rerunning the package tests on a module after it's been installed, I had been working on the idea of installing tests along with the code. This would require a few things:
1. A place to install the tests. 2. A way to save the test run history. 3. Possible cooperation from the CPAN, CPANPLUS, CPANM and other maintainers (see point 1). Saving tests could be configurable and then you'd have a test runner which would run all of the tests you've saved. The main thing to keep in mind is that some tests will fail this way (unless you manually hack them to work, such as many database tests or other tests which require resources). So what you want to do when you install a new module is to rerun the "installed" tests and note when you get *different* failures (it's harder than that, to be fair). To do this you need to save the test history and I had started that with https://github.com/Ovid/app--prove--history, but it's an awful hack which I hadn't gotten around to finishing. I'll be at the QA Hackathon here in Amsterdam this weekend, so maybe I should resurrect this idea? Cheers, Ovid -- Live and work overseas - http://overseas-exile.blogspot.com/ Buy the book - http://www.oreilly.com/catalog/perlhks/ Tech blog - http://blogs.perl.org/users/ovid/ Twitter - http://twitter.com/OvidPerl/ ----- Original Message ---- > From: Jozef Kutej <jo...@kutej.net> > To: perl-qa@perl.org > Sent: Tue, 12 April, 2011 17:50:57 > Subject: post-install testing > > Hi, > > <cite>It turned out that there is quite a lot that can go wrong.</cite> > > Found this gem in our internal wiki. :-) > > My question is regarding the post-install testing. Normally the test are run > before installation and then discarded with all the rest of the distribution > files. But what possibilities do we have about testing of already installed > code? Is anyone working on this concept? > > Cheers, > Jozef > >
