On Wed, February 25, 2009 6:06 pm, Michael G Schwern wrote:
$ prove --exec 'cat -' test.dummy
test
Now you can write TAP and finish with ctrl-d. But test.dummy has to
exist.
/dev/null works for me.
Perhaps you could post your tricks:
http://perlmonks.org/?node=Meditations#post
On Thu, October 23, 2008 10:37 am, chromatic wrote:
I don't care about backchannel communication between other authors and
CPAN
Testers, but how can you blame Shlomi for thinking that public humiliation
isn't a vital component of Kwalitee? There's prior art:
Someone who's actually looked at this stuff may want to update
http://en.wikipedia.org/wiki/Test_Anything_Protocol
I think there's also stuff on that page that needs updating
re: Test::Harness 3.
On Tue, May 13, 2008 2:44 pm, chromatic wrote:
PHP's Symfony has a test framework called lime,
On Sun, April 6, 2008 9:28 pm, Gabor Szabo wrote:
Is there a W3C validator that works locally on my computer?
You mean an X?HTML validator?
I haven't used it, but:
http://htmlhelp.com/tools/validator/offline/index.html.en
On Sun, April 6, 2008 9:28 pm, Gabor Szabo wrote:
Is there a W3C validator that works locally on my computer?
All the modules I found so far use the http://validator.w3.org/ service
including Test::HTML::W3C but that's not really usable in a frequently
running test suit.
The source for that
On Sun, January 6, 2008 4:54 pm, demerphq wrote:
So we are told the way to mark a module as development is to use an
underbar in the version number:
$VERSION= 1.23_01;
but this will produce warnings if you assert a required version number, as
the version isn't numeric.
So the standard
On Tue, July 31, 2007 9:56 pm, chromatic wrote:
On Tuesday 31 July 2007 20:25:15 Salve J. Nilsen wrote:
Turning off syntax checking of your POD is comparable to not turning on
warnings in your code. Now would you publish code developed without
use
warnings;?
Now that's just silly.
Is it?
Michael G Schwern wrote:
print TAP version 15\n;
print 1..1\n;
print # Information\n;
print not ok 1\n;
print ! Failure\n;
I'd really not like to see meaningful punctuation. How about
diag Failure\n. Or even levels of keywords debug/info/notice/warning/
David Cantrell wrote:
Michael G Schwern wrote:
First thing is breaks, and probably most important: No warnings.
Any test suite that blithely ignores warnings is BROKEN.
There are two types of warning. First, those which you deliberately
spit out, like use of foo() is deprecated, please
On 14 Mar 2007, at 07:29, chromatic wrote:
The problem is that there's no way to tell that that information
sent to
Test::Builder-diag() is diagnostic information for the tests
because once it
goes out on STDERR, it could be anything.
So we seem to have two reasonably sensible options on
Test::Builder has a method use_numbers to turn off test numbering; this
can be useful when running tests in different processes. But the doc
says:
Most useful when you can't depend on the test output order, such as when
threads or forking is involved.
Test::Harness will accept either, but
On Thu, Jul 13, 2006 at 02:29:38PM +0300, Gabor Szabo wrote:
On 7/13/06, Fergal Daly [EMAIL PROTECTED] wrote:
I could change it so that it tries to figure out whether it's being
used for real or not and disable the END block code but that's stress
and hassle. As a module author, as far as I'm
On Sun, Apr 23, 2006 at 11:01:17AM +0200, Marcus Holland-Moritz wrote:
The only thing worth mentioning is that with perl 5.003,
the following happens:
[EMAIL PROTECTED] $ perl5.003 Makefile.PL
Can't locate ExtUtils/Command.pm in @INC at Makefile.PL line 4.
On Mon, Apr 03, 2006 at 10:32:12PM +1000, Adam Kennedy wrote:
Yitzchak Scott-Thoennes wrote:
On Sat, Mar 11, 2006 at 10:20:29AM +0100, Tels wrote:
B when it breaks, end-users cannot fix the problem for themselves, they
need to bug the author and he has to release a new version. (Good luck
On Sat, Mar 11, 2006 at 10:20:29AM +0100, Tels wrote:
B when it breaks, end-users cannot fix the problem for themselves, they
need to bug the author and he has to release a new version. (Good luck
with that with sparsely maintained modules...)
Last time this happened to me, I just replaced
I remember working with some module that had tests something like:
use Test::More;
plan tests = numtests();
...
is($foo, $bar, 'foo is bar');
sub numtests { 13 }
So that when you added a new test to the bottom, the number to modify
was right there also. Ring a bell with anyone?
On Mon, Feb 20, 2006 at 11:36:27AM +, Barbie wrote:
12. System is incompatible with the package.
Linux::, Win32::, Mac:: modules. Irreconcilable differences.
Not sure how you would cover this, but point 12 seems to possibly fit.
POSIX.pm is created for the platform it's installed
On Mon, Feb 06, 2006 at 08:16:11AM +0200, Offer Kaye wrote:
OT question - why is Scalar-List-Utils listed as CORE? It is not
part of the Perl5 core
http://perldoc.perl.org/perl58delta.html#New-Modules-and-Pragmata
On Thu, Feb 02, 2006 at 02:56:09AM -0800, Tyler MacDonald wrote:
A new module doesn't need to be added to the core, so long as there
is a way that we can reliably detect when a person wishes to build and test
any given perl package for an objectively unselfish purpose such as
On Thu, Feb 02, 2006 at 10:01:48AM -0800, Tyler MacDonald wrote:
I strongly feel that authors should keep everything necessary
for their distribution public; either in the CPAN distribution
itself, or via a permanent publicly available version control
system.
Who's to say you won't lose interest
On Sun, Jan 29, 2006 at 12:04:22PM +0100, Tels wrote:
Just witness Graph::Dependency, it will fail when their is no META.yml
available, and what do you want me to do then? Parse Makefile.PLs?
The correct WTDI is to execute the Makefile.PL and parse the resulting
Makefile, looking for the
On Fri, Jan 27, 2006 at 03:42:58PM +0100, Tels wrote:
On Thursday 26 January 2006 15:26, Thomas Klausner wrote:
I just uploaded Module::CPANTS::Analyse to CPAN. MCA contains most of
the previous Kwalitee indicators and some code to check if one
distribution tarball conforms to those
On Tue, Jan 24, 2006 at 10:25:44PM -0500, David Golden wrote:
Jeffrey Thalhammer wrote:
* Should a test script have a shebang? What should it
be? Any flags on that?
I often see -t in a shebang. One downside of the shebang, though, is
that it's not particularly portable. As chromatic
On Mon, Jan 09, 2006 at 07:06:08PM +1100, Kirrily Robert wrote:
Does anyone else find that SKIP: { } blocks bugger up the debugger?
I'll be happily bouncing on the n key to get to round about the
vicinity of the failing test, and then blam, it sees a skipped test
and just fast-forwards
On Mon, Aug 15, 2005 at 05:58:23PM +0200, S?bastien Aperghis-Tramoni wrote:
use strict;
use Test::More tests = 2;
use Test::Exception;
use Net::Pcap;
throws_ok(
sub { Net::Pcap::lookupdev() },
'/^Usage: Net::Pcap::lookupdev\(err\)/',
calling
On Mon, Jul 04, 2005 at 02:19:16PM +0100, Paul Marquess wrote:
Whilst I'm here, when I do get around to posting a beta on CPAN, I'd prefer
it doesn't get used in anger until it has bedded-in. If I give the module a
version number like 2.000_00, will the CPAN shell ignore it?
This is often done
On Sat, Jul 02, 2005 at 12:24:12AM -0700, chromatic wrote:
On Sat, 2005-07-02 at 08:55 +0200, demerphq wrote:
The entire basis of computer science is based around the idea that if
you do the same operation to two items that are the same the end
result is the same. Without this there is no
On Fri, Jul 01, 2005 at 07:11:26AM +, Smylers wrote:
To me 'deeply' implies recursing as deep as the data structure goes, not
that there's a special rule for the top-level that's treated differently
from the others.
Nobody is saying is_deeply shouldn't be deep. If I understand
On Thu, Jun 30, 2005 at 05:09:39PM -0700, Michael G Schwern wrote:
So, I conclude that is_deeply()'s behavior is ok and something like
Test::Deep should be enhanced with an option to deal with this
problem.
So, am I correct in understanding that is_deeply will only notice
value differences,
On Fri, Apr 01, 2005 at 09:00:17PM +0200, Thomas Klausner wrote:
Well, kwalitee != quality. Currently, kwalitee basically only says how
well-formed a distribution is. For my definition of well-formed :-) But I'm
always open to suggestion etc.
Since you ask...
An important part of kwalitee to
On Sat, Apr 02, 2005 at 10:43:57AM -0500, Ricardo SIGNES wrote:
* David A. Golden [EMAIL PROTECTED] [2005-04-02T05:27:18]
Andy Lester wrote:
Why is there a scoreboard? Why do we care about rankings? Why is it
necessary to compare one measure to another? What purpose is being
served?
On Mon, Mar 28, 2005 at 08:35:34PM -0800, Michael G Schwern wrote:
Whether things that are required for *testing* belong in
build_requires really depends on whether you view testing as an
integral part of the build process. This is something that is likely
to depend on the *builder*, not
On Mon, Mar 28, 2005 at 03:10:52PM -0800, Michael G Schwern wrote:
On Mon, Mar 28, 2005 at 08:42:50AM -0500, Christopher H. Laco wrote:
That's another gripe of mine about M::B and create_makefile_pl.
It puts the requires AND build_requires in the PREREQ_PM in the
Makefile.PL, which I won't
On Sun, Mar 06, 2005 at 10:32:26AM -0800, Michael G Schwern wrote:
#!/usr/bin/perl -w
use Getopt::Long;
my %Opts;
GetOptions(\%Opts, test);
sub main {
return if $Opts{test};
...the program using the functions
34 matches
Mail list logo
