On Wed, Apr 13, 2011 at 6:40 AM, Ovid wrote:
> 3. Possible cooperation from the CPAN, CPANPLUS, CPANM and other maintainers
> (see point 1).
>From the CPAN client's point of view, installing means executing
either «make install» or «./Build install». The actual installing is
done by ExtUtils::Ins
On Apr 13, 2011, at 10:16 AM, Jozef Kutej wrote:
> On 2011-04-13 06:40, Ovid wrote:
>> 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:
>>
On 2011-04-13 06:40, Ovid wrote:
> 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 th
On 2011-04-13 01:00, Michael G Schwern wrote:
> Are you talking about integrity testing, making sure the system still has all
> their pieces and they still work? Or runtime testing, essentially a
> combination of asserts and logging which run from inside the code to check
> that the system is inte
o: perl-qa@perl.org
> Sent: Tue, 12 April, 2011 17:50:57
> Subject: post-install testing
>
> Hi,
>
> It turned out that there is quite a lot that can go wrong.
>
> Found this gem in our internal wiki. :-)
>
> My question is regarding the post-install testing. Normal
On 2011.4.13 1:50 AM, Jozef Kutej wrote:
> It turned out that there is quite a lot that can go wrong.
>
> 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 a
Hi,
It turned out that there is quite a lot that can go wrong.
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
