chromatic wrote:
> I just went through a sampling of fail reports for my stuff. There was one
> legitimate packaging bug, and a couple of legitimate errors due to updates to
> Perl. About 35% of the other reports are these.
>
> I love the "Illegal seek" error message:
>
> http://www.nnt
On Saturday 22 December 2007 21:58:46 David Golden wrote:
> These are not simple modules. Assuming that some smoker can get these
> to successfully send you a report, then which scenario seems more
> likely:
>
> (a) that the smoker's installation is fundamentally broken
> (b) that your distributi
On Dec 22, 2007 8:26 PM, chromatic <[EMAIL PROTECTED]> wrote:
> CPAN Testers reporting failures in every module they test and not stopping to
> ask "Hey, is it possible that not everything else in the world is broken?" is
> *not* an example of CPAN Testers working as expected.
>
> Environments wher
chromatic wrote:
> On Saturday 22 December 2007 16:48:29 Michael G Schwern wrote:
>> The "I installed to a directory with a space in the path" is an example of
>> CPAN Testers working as expected. It found and highlighted an annoying bug
>> that the rest of us either ignore or work around.
>
> CP
On Saturday 22 December 2007 16:48:29 Michael G Schwern wrote:
> The "I installed to a directory with a space in the path" is an example of
> CPAN Testers working as expected. It found and highlighted an annoying bug
> that the rest of us either ignore or work around.
CPAN Testers reporting fail
Matisse Enzer wrote:
> I respectfully suggest that maybe there is another way of looking at it,
> where the install process (governed by Makefile.PL/Build.PL) could
> possibly be a "test driven installation" process:
>
>use Test::More tests => 23;
>unlike( $^X,qr{\s}, q{'$^X' has no spaces
On Dec 22, 2007 6:03 PM, Matisse Enzer <[EMAIL PROTECTED]> wrote:
> I respectfully suggest that maybe there is another way of looking at
> it, where the install process (governed by Makefile.PL/Build.PL) could
> possibly be a "test driven installation" process:
>
> use Test::More tests => 23;
>
On Dec 22, 2007, at 12:52 PM, chromatic wrote:
Let me rephrase then.
I feel dirty writing tests just to trip up testers who can't set up
working
testing environments.
I call those "non-functional tests", because they have very little
to do with
things that actually matter in my software
On 22/12/2007, David Golden <[EMAIL PROTECTED]> wrote:
> On Dec 22, 2007 3:52 PM, chromatic <[EMAIL PROTECTED]> wrote:
> > Let me rephrase then.
> >
> > I feel dirty writing tests just to trip up testers who can't set up working
> > testing environments.
>
> Is this really a problem? Let me flip t
On Dec 22, 2007 3:52 PM, chromatic <[EMAIL PROTECTED]> wrote:
> Let me rephrase then.
>
> I feel dirty writing tests just to trip up testers who can't set up working
> testing environments.
Is this really a problem? Let me flip this around -- I get very few
problems of this sort for CPAN::Reporte
On Saturday 22 December 2007 12:44:12 David Golden wrote:
> On Dec 22, 2007 2:12 PM, chromatic <[EMAIL PROTECTED]> wrote:
> > I'm not sure how to write a test for "Tester's installation of Perl is
> > fatally broken and can't actually install anything."
> Oh, come on. This is Perl, after all.
>
On Dec 22, 2007 2:12 PM, chromatic <[EMAIL PROTECTED]> wrote:
> I agree in principle, but in practice I seem to get a lot of failure reports
> from someone who's installed Perl on Windows into a directory with spaces in
> the name, and whatever installer there is just can't cope with that
> situati
On Saturday 22 December 2007 05:22:05 Andreas J. Koenig wrote:
> 1. You get a fail report with an error message that doesn't tell you
> exactly what went wrong.
>
> 2. You rewrite your test in a way that it does tell you more.
>
> 3. Release.
>
> 4. If you now understand the problem, fix it, el
> On Sat, 22 Dec 2007 14:22:05 +0100, [EMAIL PROTECTED] (Andreas J. Koenig)
> said:
> 1. You get a fail report with an error message that doesn't tell you
>exactly what went wrong.
> 2. You rewrite your test in a way that it does tell you more.
> 3. Release.
> 4. If you n
> On Fri, 21 Dec 2007 13:34:49 -0600 (CST), Dave Rolsky <[EMAIL PROTECTED]>
> said:
> However, usually I end up needing to investigate aspects of the
> testers platform, often by having them run snippets of Perl code from
> the shell, or asking them to try a patch. There's not much
15 matches
Mail list logo
