Announcing a Testing SDK! It's also the first SDK, AFAIK.
This SDK bundles
Test::Harness 1.23
Test::Inline0.10
Test::Simple0.16
into one easy to install tarball. It's been uploaded to CPAN.
Not quite sure how the CPAN shell's going to deal with it.
http://www.pobox.com
Pod::Tests is now Test::Inline and distributed as such. The
Pod::Tests module remains, but it's just the POD parser.
http://www.pobox.com/~schwern/src/Test-Inline-0.10.tar.gz
There are two major API changes.
First, the syntax for the code examples has changed. Instead of
"=also begin/end exam
On Thu, Aug 23, 2001 at 06:45:26AM +0900, Tatsuhiko Miyagawa wrote:
> Title says it all :-)
It's in. New version will work back to 5.004 now. Thanks!
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee I
On Tue, Aug 28, 2001 at 07:56:30PM -0400, Kirrily 'Skud' Robert wrote:
> Checking POD coverage...
> Test::Simple 33% *
> Test::Harness 33% *
That's actually correct, as there are only three public-looking
functions in Test::Simple.
On Tue, Aug 28, 2001 at 09:19:08PM +0100, [EMAIL PROTECTED] wrote:
> To portably run:
>
> pod2text lib/Some/Module.pm >README
Don't use pod2text, use Pod::Text.
use Pod::Text;
my $parser = $formatter->new;
$parser->parse_from_file ($module, 'README');
that's all any modern pod2te
This script...
#!/usr/bin/perl -w
use strict;
use Pod::Coverage;
use ExtUtils::Installed;
my $m = ExtUtils::Installed->new;
my @modules = $m->modules();
print "Checking POD coverage...\n";
my %coverage;
foreach my $mod (@modules) {
my $pc = new Pod::Coverage package => $mod;
$coverag
Umm, let's not go overboard. The t/TEST script says
# This is written in a peculiar style, since we're trying to avoid
# most of the constructs we'll be testing for.
and the same obviously applies to some of the t/*/*.t tests.
I'm sure Larry would have found getting perl5 off the ground harder
PS When you write these new tests, use Test::More, please.
--
Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/
Perl6 Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
...and I pull out the Magnum from under the desk where I keep it in case
someone la
On Tue, Aug 28, 2001 at 03:55:09PM +0100, Tim Bunce wrote:
> Probably best to leave at least t/base/* and t/cmd/* alone.
Sorry, I thought I said that.
Concentrate on t/op/, t/io/, t/pod/ and the tests in lib/.
The op ones you're going to have to evaulate on a case-by-case basis
whether or not i
Some people have requested an update on the list of untested modules.
This is the list as of almost three months ago, I don't think it's
changed much.
As you may know, I have a standing offer to donate $500 to YAS upon
every core module having basic testing coverage.
AutoSplit
CGI::Apache
CGI::C
On Tue, Aug 28, 2001 at 02:12:46PM +0100, Robin Houston wrote:
> Michael Schwern wrote:
> > Ah HA! I've been wondering why nobody ever thinks to write a simple
> > ok() function for their tests! perlhack has bad testing advice.
>
> Could you explain the advantage of having a "simple ok() functi
[I'm being very slack in moving things between the qa and london.pm
lists, so far no-one has shouted at me, but apologies in advance]
On Tue, Aug 28, 2001 at 02:31:58PM +0200, Paul Johnson wrote:
> That keeps README up to date with the NAME and DESCRIPTION sections from
> the pod in Cover.pm.
Th
(ok, I know there's 0.04 now, but I've deleted that announcement)
The thing I'd *really* like to see in this now is the ability to run
it on arbitrary code - not just installed modules. i.e. I want to add
it to a 'build' process, that will automatically reject code that isn't
fully documented -
I just updated the perlhack man page to include this:
t/op/pack.t has a sensible ok() function, but if it didn't
we could write one easily.
my $test = 1;
sub ok {
my($ok) = @_;
my $out = '';
$out = "not " unless $ok;
$out .= "ok $
14 matches
Mail list logo
