gt; :)
>
> Apologies for the delay in replying. Pull requests to github get
> -slightly- better turnaround time.
>
> TAP::Harness was introduced in 5.10.1 - I'm pretty sure our current
> perl5 build requirement is 5.10.0 - I'm not sure if we are ready to
> bump that u
ness
invokes TAP::Harness with.
'trap' is fatal for older TAP::Harness versions, and hence causes t/harness and
thus the tests to abort.
Patch attached that makes it conditional.
>From c683753b06a08ab32e051dcaaa79c62dc9abe5b9 Mon Sep 17 00:00:00 2001
From: Nicholas Clark
Date: Sat,
slightly-
better turnaround time.
TAP::Harness was introduced in 5.10.1 - I'm pretty sure our current perl5 build
requirement is 5.10.0 - I'm not sure if we are ready to bump that up.
Additionally, this patch no longer cleanly applies.
--
Will "Coke" Coleda
slightly-
better turnaround time.
TAP::Harness was introduced in 5.10.1 - I'm pretty sure our current perl5 build
requirement is 5.10.0 - I'm not sure if we are ready to bump that up.
Additionally, this patch no cleanly applies.
--
Will "Coke" Coleda
it.
Doesn't add noticeable spectest speedups, sorry (just prettier code :)>From 74a3d77b31d2449fb62c3968768a0e92591eb077 Mon Sep 17 00:00:00 2001
From: Anthony Parsons
Date: Mon, 26 Jan 2015 22:16:35 +
Subject: [PATCH] Switch to using TAP::Harness directly in t/harness
The previous code woul
# from Parrot via RT
# on Tuesday 04 September 2007 01:30 am:
>With TAP::Parser, the attached patch and Parrot/TAP/Harness.pm in the
>current directory[1], the tests can be run as:
>
> runtests --harness Parrot::TAP::Harness $(perl t/harness --files)
The runtests code has been ref
ent directory[1], the tests can be run as:
runtests --harness Parrot::TAP::Harness $(perl t/harness --files)
Running all of the tests is easy,
runtests --harness Parrot::TAP::Harness -r t language
but the t/harness tendency to only run ~80% of the tests means that will
take a very long time (and f
# from Gabor Szabo
# on Saturday 01 September 2007 01:35 am:
>Regarding Parrot, I think there was some discussion of moving it to
> use TAP::Harness and to use Smolder to collect the TAP based results.
Indeed.
We determined that the main task is refactoring all of the t/harness
file
On 7/1/06, Michael G Schwern <[EMAIL PROTECTED]> wrote:
As my flight is delayed I'll try to make a stab at posting up the basic design.
The whole point of replacing the Perl QA wiki was to have a public
place for the TAP::Harness design to live. :)
http://perl-qa.yi.org/index.php/T
Geoffrey Young wrote:
> I've mentioned the idea of making it simple to use
> plan() and Test::More functions before
blarg... insert "separately" ^ here. all the rest is pretty simple
already :)
--Geoff
sorry for dropping in on this late, but it was a holiday weekend :)
> * How can I help?
>
> Provide use cases, what would you want to do with Test::Harness if you
> could? What are you doing with Straps? What features do other
> testing systems (JUnit, for example) have that you'd like to see i
On Jul 3, 2006, at 4:29 AM, Rafael Garcia-Suarez wrote:
What about prove(1) ? Are you going to make a version of it that uses
TAP::Harness ? And it so, will it be removed it from T::H ? (I hope
not,
since it's part of the core). Or have a fork ?
No, prove will be in both Test::Harnes
On Sunday 02 July 2006 23:37, Adam Kennedy wrote:
> > The most up-to-date Test-Run code is here:
> >
> > http://svn.berlios.de/svnroot/repos/web-cpan/Test-Harness-NG/
> >
> > I don't mind giving Subversion access to the repository to anyone who
> > registers in http://developer.berlios.de/ and is e
"Michael G Schwern" wrote in perl.qa :
> * What about Test::Harness?
>
> Test::Harness remains its own thing.
>
> At some point in the future Test::Harness will likely be gutted and
> turned into a thin wrapper around TAP::Harness. I'm not caring about
> this r
Michael G Schwern wrote:
On 7/1/06, Yuval Kogman <[EMAIL PROTECTED]> wrote:
Please look at Test::TAP::Model and the horrrible hooks it goes
through to make things work.
I'd love to have a SAX like event-handler model for TAP through
TAP::Harness so that I can construct Test:
The most up-to-date Test-Run code is here:
http://svn.berlios.de/svnroot/repos/web-cpan/Test-Harness-NG/
I don't mind giving Subversion access to the repository to anyone who
registers in http://developer.berlios.de/ and is either a CPAN contributor,
or has sent me one patch for me to commit.
* How can I help?
Provide use cases, what would you want to do with Test::Harness if you
could? What are you doing with Straps? What features do other
testing systems (JUnit, for example) have that you'd like to see in
Perl? Once I post the design, pick it to pieces.
I know I mentioned it to
currently forces me to process the test results in
series - which means that I can wait longer than necessary to
discover a test failure that's been processed, but is waiting behind
a longer running test script.
I'd like TAP::Harness to be able to accept multiple streams of TAP
On Sunday 02 July 2006 01:24, Michael G Schwern wrote:
> On 7/1/06, Shlomi Fish <[EMAIL PROTECTED]> wrote:
> > One thing I'm wondering about is
> > whether you are going to code all of this into TAP::Harness from scratch.
>
> I believe I mentioned, I intend t
On Sat, Jul 01, 2006 at 16:59:24 -0500, Michael G Schwern wrote:
> Yes, it is SAXy. You have Adam to thank for that.
>
> As my flight is delayed I'll try to make a stab at posting up the basic
> design.
Another issue we had at work when I was abusing TAP for our C++ UT
framework was that we ne
On 7/1/06, Yuval Kogman <[EMAIL PROTECTED]> wrote:
Another issue we had at work when I was abusing TAP for our C++ UT
framework was that we needed more levels of nesting (TAP only
supports streams and test cases - I was handling many test cases in
the same stream, for nested modules... I faked "f
On 7/1/06, Shlomi Fish <[EMAIL PROTECTED]> wrote:
One thing I'm wondering about is
whether you are going to code all of this into TAP::Harness from scratch.
I believe I mentioned, I intend to steal lots of code from
Test::Harness and Straps. "Steal" in the cut & pas
On Saturday 01 July 2006 14:52, Michael G Schwern wrote:
> There are at least two approaches I could think of that fit the
> existing design. One is to replace the tokenizer. The other is to
> create a TAP source which converts from your protocol into TAP. The
> latter is probably easiest and s
On 7/1/06, Steve Peters <[EMAIL PROTECTED]> wrote:
On Sat, Jul 01, 2006 at 08:45:02PM +0100, Fergal Daly wrote:
> This might seem like an odd question but will it be tightly tied to
> TAP or will it be possible to use another protocol or an extension to
> TAP?
Pluggable testing protocols, perhap
On 7/1/06, Yuval Kogman <[EMAIL PROTECTED]> wrote:
Please look at Test::TAP::Model and the horrrible hooks it goes
through to make things work.
I'd love to have a SAX like event-handler model for TAP through
TAP::Harness so that I can construct Test::TAP::Model objects in a
Please look at Test::TAP::Model and the horrrible hooks it goes
through to make things work.
I'd love to have a SAX like event-handler model for TAP through
TAP::Harness so that I can construct Test::TAP::Model objects in a
cleaner way (without the parser-is-the-model and all that
On Saturday 01 July 2006 14:24, Shlomi Fish wrote:
> I'd hate to see some duplicate effort.
Test::Run has really curious licensing; I'm not interested in redistributing
that code under all of those licenses.
-- c
On Saturday 01 July 2006 22:36, Michael G Schwern wrote:
> Those of you who were/are at the YAPC Hackathon might know, I've begun
> work on what started as Test::Harness 3 and is now TAP::Harness. This
> is brand new, ground up rewrite of the idea of a harness for TAP
> sources (
On 01/07/06, Andy Lester <[EMAIL PROTECTED]> wrote:
On Jul 1, 2006, at 2:45 PM, Fergal Daly wrote:
> This might seem like an odd question but will it be tightly tied to
> TAP or will it be possible to use another protocol or an extension to
> TAP?
Yes. It is about TAP. That
On Sat, Jul 01, 2006 at 02:36:37PM -0500, Michael G Schwern wrote:
> Right now the use cases I have in mind include things such as
> parallelized test runs, fancy GUI and HTML outputs (for example,
> Provide use cases, what would you want to do with Test::Harness if you
> could? What are you doi
On Jul 1, 2006, at 2:45 PM, Fergal Daly wrote:
This might seem like an odd question but will it be tightly tied to
TAP or will it be possible to use another protocol or an extension to
TAP?
Yes. It is about TAP. That's why it's TAP::Harness.
xoa
--
Andy Lester => [EM
On Sat, Jul 01, 2006 at 08:45:02PM +0100, Fergal Daly wrote:
> This might seem like an odd question but will it be tightly tied to
> TAP or will it be possible to use another protocol or an extension to
> TAP?
Pluggable testing protocols, perhaps. They would need to follow some
similar ground ru
hat started as Test::Harness 3 and is now TAP::Harness. This
is brand new, ground up rewrite of the idea of a harness for TAP
sources (a foo.t file is a TAP source). Its being designed to be
extendable to handle all the things we'd like to do with Test::Harness
over the last few years without
Those of you who were/are at the YAPC Hackathon might know, I've begun
work on what started as Test::Harness 3 and is now TAP::Harness. This
is brand new, ground up rewrite of the idea of a harness for TAP
sources (a foo.t file is a TAP source). Its being designed to be
extendable to handl
34 matches
Mail list logo
