On Tue, Feb 23, 2010 at 9:13 PM, Andreas J. Koenig <andreas.koenig.7os6v...@franz.ak.mind.de> wrote: > > The signature test isn't really a test. Its not testing that the code > > does its job, its testing that it passes its signature. Its not a > > functionality test, its a security measure, and doesn't really belong > > in the test suite. At best its an author check of the integrity of > > the distribution not to be distributed. > > I can only disagree. It's certainly of value to know that integrity > checks work somewhere else and not only on author's home box before > packaging.
We have an entire system specifically for that, called CPAN Testers. There is no reason to impose this kind of thing on end users, as the failure does not actually prevent the module from working, and the end user will have no way to resolve the problem. As for the test failing, the problem here is that in order to be work correctly, the test must be run before Makefile.PL is run at the very least, or ideally they should be run before the tarball is extracted. The defect in the test is thus unresolvable, and thus the test should be dropped for end users. Adam K
