Gabor Szabo wrote:
On 9/7/06, Salve J Nilsen [EMAIL PROTECTED] wrote:
Thomas Klausner wrote:
Oh, and if you want to join the fun and help a bit, here's a (probably
incomplete) list of tasks:
- Metrics:
[snip]
Would the metrics for community support channels that were suggested a
while
- Original Message
From: Michael G Schwern [EMAIL PROTECTED]
Ah, crud. I need to support it then. Bummer. I'll try to get a release
out there when I can, then.
Don't bother, its a poorly designed feature and likely unused. I don't want
to see it pushed forward into TAP.
OK,
Adam Kennedy wrote:
Salve J Nilsen wrote:
Thomas Klausner wrote:
Oh, and if you want to join the fun and help a bit, here's a (probably
incomplete) list of tasks:
- Metrics:
[snip]
Would the metrics for community support channels that were suggested a
while ago be welcome? (The discussion
In a module I have just started to maintain there were 0 tests
but there were several exampes with their expected output.
As I would like to keep the examples and I would like to have tests
but I don't want to duplicate this code I added a test t/sample.t
that would run each one of the example
Gabor Szabo wrote:
(system code out 2err)...
So far I have encountered only one problem with this, when I run
./Build testcover I don't get the coverage report from these
example scripts.
So what do you think about using examples as tests?
How could I convince Devel::Cover to collect coverage
Last week I was at a testing conference with Acme and he came up with the idea
of installing tests. He looked into hacking Module::Build and
ExtUtils::MakeMaker. He also considered hacking CPAN.pm and CPANPLUS.pm.
While I don't know if he plans to continue working on this idea, he said he
On 11 Sep 2006, at 14:02, Ovid wrote:
Last week I was at a testing conference with Acme and he came up
with the idea of installing tests. He looked into hacking
Module::Build and ExtUtils::MakeMaker. He also considered hacking
CPAN.pm and CPANPLUS.pm. While I don't know if he plans to
Ovid wrote:
I love this idea, but here are some issues that we spotted:
1. How does one install tests for modules already installed?
2. If you install a module with already failing tests, you need to track what
the failures are so you can note different failures when you run the test suite
On Sep 11, 2006, at 8:02 AM, Ovid wrote:
Last week I was at a testing conference with Acme and he came up
with the idea of installing tests. He looked into hacking
Module::Build and ExtUtils::MakeMaker. He also considered hacking
CPAN.pm and CPANPLUS.pm. While I don't know if he plans
Ovid wrote:
- Corrected the grammar to allow for a plan of 1..0 (infinite
stream).
1..0 is currently used as part of the skip all syntax.
1..0 # skip Because I said so
Perhaps an infinite stream is just 1.. ?
- Original Message
From: Michael G Schwern [EMAIL PROTECTED]
Ovid wrote:
- Corrected the grammar to allow for a plan of 1..0 (infinite
stream).
1..0 is currently used as part of the skip all syntax.
1..0 # skip Because I said so
Perhaps an infinite stream
On Sep 11, 2006, at 9:58 AM, Ovid wrote:
- Original Message
From: Michael G Schwern [EMAIL PROTECTED]
Ovid wrote:
- Corrected the grammar to allow for a plan of
1..0 (infinite
stream).
1..0 is currently used as part of the skip all syntax.
1..0 # skip
- Original Message
From: Chris Dolan [EMAIL PROTECTED]
How is that infinite stream different from the no_plan case? Is it
truly infinite or just undetermined? That is, are you trying to code
for the following use case?
use Test::More test = 'Inf';
use LWP::Simple qw(get);
Torsten Schoenfeld wrote:
Yeah, this is hand-rolled stuff. One example:
http://search.cpan.org/src/TSCH/Glib-1.140/t/7.t
As the comment in there says ...
we do not use Test::More or even Test::Simple because we need to test
order of execution... the ok() funcs from those modules
Thomas Klausner wrote:
The one advantage of dedicated examples for me is that I can take that
example file (mostly downloaded from search.cpan.org), run it, modifiy
it, run it etc.
Cutting and pasting from the docs works as well, no network required. And its
going to be the example for the
- Original Message
From: Shlomi Fish
In other news, Test::Run now makes use of TAPx::Parser to parse the TAP. It
still collects the statistics on its own, because I couldn't remember whether
TAPx::Parser does that or not, and it was too much work to do at one time.
I've run into a possible bug with TAPx::Parser. According to
http://search.cpan.org/dist/TAP/TAP.pm#The_plan:
The plan cannot appear in the middle of the output,
nor can it appear more than once.
I'm getting parse errors because comments are output after the plan:
TAPx-Parser $ perl
Ovid wrote:
I've run into a possible bug with TAPx::Parser. According to
http://search.cpan.org/dist/TAP/TAP.pm#The_plan:
The plan cannot appear in the middle of the output,
nor can it appear more than once.
I'm getting parse errors because comments are output after the plan:
Ovid wrote:
Last week I was at a testing conference with Acme and he came up with the idea
of installing tests. He looked into hacking Module::Build and
ExtUtils::MakeMaker. He also considered hacking CPAN.pm and CPANPLUS.pm.
While I don't know if he plans to continue working on this idea,
On Sep 11, 2006, at 7:08 PM, Randy W. Sims wrote:
Ovid wrote:
Last week I was at a testing conference with Acme and he came up
with the idea of installing tests. He looked into hacking
Module::Build and ExtUtils::MakeMaker. He also considered hacking
CPAN.pm and CPANPLUS.pm. While I
Of course some authors don't care about having a community around their
software, and some don't consider their CPAN package as important or
big enough to warrant a community (despite it probably being licensed
with an open source-friendly license). These people are entirely free to
continue
Going along the path of testing the examples in my distribution,
I think it could be generalized. What do you think about this?
Gabor
=head1 NAME
Test::Example - Check if all the examples in the distribution work correctly
=head1 SYNOPSIS
use Test::Example;
test_all_examples();
or
22 matches
Mail list logo
