I have just discovered the cpants and was wondering why only version
1.2.3 of bioperl has made it in and not the latest version 1.4?
Does anyone have any ideas about this?
Cheers
Nathan
On 10/24/06, Ovid [EMAIL PROTECTED] wrote:
now it adds boilerplate.t). I forgot to add to the MANIFEST any of the
tests for the actual functionality :(
I it would be valuable to have a metric which checks to see if any
tests beyond the basics are included. Of course, this could well be
Hi!
On Tue, Oct 24, 2006 at 03:13:08PM +0100, Nathan Haigh wrote:
I have just discovered the cpants and was wondering why only version
1.2.3 of bioperl has made it in and not the latest version 1.4?
Does anyone have any ideas about this?
CPANTS currently seems to have some problems with
Nathan Haigh wrote:
I have just discovered the cpants and was wondering why only version
1.2.3 of bioperl has made it in and not the latest version 1.4?
Does anyone have any ideas about this?
I noticed the same thing. A module I released over a week ago is still
stuck at version n-1. I think
Michael G Schwern wrote:
Christopher H. Laco wrote:
Shouldn't all tests be set to use tainting?
And by extension, shouldn't all modules run under -T?
(Just curious)
That would be nice, but tainting is a pain in the ass and not something I'd
be willing to universally inflict on all module
Adrian Howard wrote:
On 5 Oct 2006, at 15:11, Paul Beckingham wrote:
Recently I was required to create another flavor of test harness that
runs tests, then captures and stores output.
The nature of my testing means that I am running millions of tests,
and the resultant captured output is
Jonathan Rockway wrote:
I like the YAML syntax, but can we live with:
got: |
this is line 1
this is line 2
expected: |
this is line 1
this is line 2
Instead? That way a real YAML parser can parse the output of TAP, which
could be important for adoption by other languages. Rather
Christopher H. Laco wrote:
While trying to install the latest PPI from svn, I noticed that running
'dmake test' passed, and 'prove -b t/' failed.
As more and more people use Module::Install, it seems more and more
transient build/test related modules are being stuffed in the inc/
directory.
Ovid wrote:
From: Florian Scharinger
I have troubles building Test-Simple-0.64 on a standard SL3 machine:
snip
several threading related tests fail, e.g.:
snip
-bash-2.05b$ perl -V
Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
From the Test::Simple
Jonathan Rockway wrote:
True. On the flip side, there's nothing more irritating that flipping
PerlTaintCheck On only to find out a crapload of modules don't run under
taint. And that's assuming you have control over whether the flag is set
of not. :-/
Maybe an example would help me
10 matches
Mail list logo