On 3/8/07, Adam Kennedy <[EMAIL PROTECTED]> wrote:
Andy Armstrong wrote:
>> Otherwise when dealing with TAP streams that don't have a concept of
>> an exit code or a seperate error channel, the most common example
>> being web testing, we're left high and dry.
>
> In which case you'd just omit th
On 9 Mar 2007, at 01:44, Adam Kennedy wrote:
Like I said, we can't use them for anything that matters :)
It's just occurred to me that it makes it easier to write tests for
the harness too :)
I can't quite get my head round the objection to the idea that a TAP
transcript could be a comple
On 3/8/07, Andy Armstrong <[EMAIL PROTECTED]> wrote:
I propose that we prefix lines from STDERR with '! ' in the same way
that '# ' is used for diagnostics. wstat and exit can just be
wstat 256
exit 1
How about this?
wstat: 256
exit: 1
YAML, YAML, do!
;)
On 9 Mar 2007, at 00:28, Adam Kennedy wrote:
I propose that we prefix lines from STDERR with '! ' in the same
way that '# ' is used for diagnostics. wstat and exit can just be
wstat 256
exit 1
The problem with STDERR and exit is that we can't actually use them
for anything significant.
W
I propose that we prefix lines from STDERR with '! ' in the same way
that '# ' is used for diagnostics. wstat and exit can just be
wstat 256
exit 1
The problem with STDERR and exit is that we can't actually use them for
anything significant.
Otherwise when dealing with TAP streams that don
Thanks for the help! For people searching the archives in the future, what I
had to do was set the HARNESS_PERL environment variable to "call" (in
windows, for an executable TAP written with libtap).
The following works as well:
===
use TAPx::Harness;
my $harness = TAPx::Harness->new( { exec
On 8 Mar 2007, at 22:47, Eric Hacker wrote:
I propose that we prefix lines from STDERR with '! ' in the same way
that '# ' is used for diagnostics. wstat and exit can just be
wstat 256
exit 1
How about this?
wstat: 256
exit: 1
YAML, YAML, do!
Doesn't look like TAP though :)
--
Andy A
On 8 Mar 2007, at 21:55, Michael G Schwern wrote:
Michael G Schwern wrote:
Stop. Stop stop stop! Stop right there.
Umm, people might not realize that I tend to be a bit over dramatic
and
didn't actually mean to shut down the discussion.
"He's not the Messiah. He's a very naughty boy". O
Michael G Schwern wrote:
> Stop. Stop stop stop! Stop right there.
Umm, people might not realize that I tend to be a bit over dramatic and
didn't actually mean to shut down the discussion.
Julien Beasley wrote:
> Just to clarify.. I'm fine with running Test::Harness instead of
> TAPx::Harness. One of the things that drew me to Test::Harness was reading
> about TAP and how it's language agnostic. But putting in a non perl
> executable in runtests certainly doesn't work! I want to ta
Just to clarify.. I'm fine with running Test::Harness instead of
TAPx::Harness. One of the things that drew me to Test::Harness was reading
about TAP and how it's language agnostic. But putting in a non perl
executable in runtests certainly doesn't work! I want to take advantage of
the languagage
I'm trying to get my project to move to TAP -- we have some perl test files
and some C++ test files. Let's say I have 2 files: test.pl, and test.exe,
the former is a perl program and the latter is a compiled program that
outputs TAP.
How do I use TAPx::Harness to run them both? I'm not really sur
In article <[EMAIL PROTECTED]>, Christopher H. Laco
<[EMAIL PROTECTED]> wrote:
> Paul Beckingham wrote:
> > I'm wanting sparse output:
> >
> > 1..100 sparse
> > 12 not ok
> > 83 not ok
> >
> But how do you know "23 ok" if you were never told that it ran ok?
For your sparse driver,
--- Nicholas Clark <[EMAIL PROTECTED]> wrote:
> > But how do you know "23 ok" if you were never told that it ran ok?
>
> Surely one can post-process a regular TAP file to "sparse" output?
> And only do so if the TAP file is valid non-sparse output.
>
> This seems safer than generating it by def
On 8 Mar 2007, at 16:34, Nicholas Clark wrote:
But how do you know "23 ok" if you were never told that it ran ok?
Surely one can post-process a regular TAP file to "sparse" output?
And only do so if the TAP file is valid non-sparse output.
Or post process it using gzip...
--
Andy Armstrong,
On Thu, Mar 08, 2007 at 11:05:31AM -0500, Christopher H. Laco wrote:
> Paul Beckingham wrote:
> > Because I need to retain the output of all tests, and those files get
> > large, but mostly because of the sheer redundancy.
> >
> >
> >
>
> But how do you know "23 ok" if you were never told tha
Paul Beckingham wrote:
> I'm wanting sparse output:
>
> 1..100 sparse
> 12 not ok
> 83 not ok
>
> Which is three lines of output, instead of 97, but contains the same
> information as:
>
> 1..100
> 1 ok
> 2 ok
> ...
> 12 not ok
> ...
> 83 not ok
> 84 o
I'm wanting sparse output:
1..100 sparse
12 not ok
83 not ok
Which is three lines of output, instead of 97, but contains the same
information as:
1..100
1 ok
2 ok
...
12 not ok
...
83 not ok
84 ok
--- Adrian Howard <[EMAIL PROTECTED]> wrote:
> In the mean time if you don't mind poking a private method you can
> do:
>
> INIT { Test::Class->runtests( Test::Class->_test_classes, +1 ) }
>
> If you do mind you could always copy'n'paste the code out into your
> subclass and rename appropriate
On 8 Mar 2007, at 11:17, Ovid wrote:
[snip]
How do I run an individual test class which inherits from
"My::Test::Class" and have the INIT block in "My::Test::Class"
dynamically determine which test class name to put there? That's
what's stumping me.
[snip]
Damn. I knew that asymmetric treatme
If you have anything to ask about testing stuff, or Test::Harness, or
any of my Test:: modules, please mail me directly.
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
Ovid wrote:
> Also at http://use.perl.org/~Ovid/journal/32614
>
> I get tired of writing this all the time:
>
> #!/usr/bin/perl
>
> use Test::More tests => 23;
> use Test::Exception;
> use Test::Differences;
> use Test::NoWarnings;
>
> ...
>
> I write that *a lot*. No more. This
On 3/7/07, Ken Williams <[EMAIL PROTECTED]> wrote:
In the specific instance we're talking about, cc_author, I wouldn't
want it in any such file, whether per-author or per-distribution; I'd
want it as a preference I can set within the cpan-testers system.
Because if I change my mind and decide I'd
Also at http://use.perl.org/~Ovid/journal/32614
I get tired of writing this all the time:
#!/usr/bin/perl
use Test::More tests => 23;
use Test::Exception;
use Test::Differences;
use Test::NoWarnings;
...
I write that *a lot*. No more. This does the same thing:
#!/usr/bin/perl
--- Adrian Howard <[EMAIL PROTECTED]> wrote:
>
> On 8 Mar 2007, at 10:44, Ovid wrote:
> [snip]
> > I cannot easily use 'Test::NoWarnings' because that adds an extra
> > test,
> > thus forcing me to use 'no_plan' with one of my tests. Is there
> some
> > other way around this?
> [snip]
>
> Do
On 8 Mar 2007, at 10:44, Ovid wrote:
[snip]
I cannot easily use 'Test::NoWarnings' because that adds an extra
test,
thus forcing me to use 'no_plan' with one of my tests. Is there some
other way around this?
[snip]
Do something like:
INIT { Test::Class->runtests( 'Foo', +1 ) }
Also, not
Reading through this I can't help but thing I've seen it all before.
The PITA test result code conversation, if you'll recall.
But when that cloned something akin to HTTP codes it was because there
looked to be only 15-20 total possible results.
And it's not meant to be extensible the way TAP
So here's a minimal test class program (v0.24):
package Foo;
use Test::More;
use Test::NoWarnings;
use base 'Test::Class';
INIT { Test::Class->runtests }
sub startup : Tests(startup => 1) { ok 1 }
sub setup : Tests(setup => 1){ ok 1 }
sub some_test : T
28 matches
Mail list logo
