Re: TAP::Harness timeout?

On Wed, Jan 29, 2014 at 6:50 AM, Todd Rinaldo wrote: > I’m looking at using TAP::Harness to process our test suite. Up to now > we’ve been using some home grown code that IMHO is a heroic attempt to > re-implement TAP::Harness. > > It seems to do everything we need with one exc

Re: TAP::Harness timeout?

Class-Moose/ Cheers, Ovid -- IT consulting, training, international recruiting        http://www.allaroundtheworld.fr/. Buy my book! - http://bit.ly/beginning_perl Live and work overseas - http://www.overseas-exile.com/ On Wednesday, 29 January 2014, 6:50, Todd Rinaldo wrote: I’m looking at u

TAP::Harness timeout?

I’m looking at using TAP::Harness to process our test suite. Up to now we’ve been using some home grown code that IMHO is a heroic attempt to re-implement TAP::Harness. It seems to do everything we need with one exception. We have rules that disallow a unit test from taking more than XXX

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

On Fri, 29 Nov 2013 01:11:23 -0800 (PST) Ovid wrote: > Hi Shlomi, > > My definitive answer would be to say "work with Leon" on this :) He's taken > over maintenance on TAP::Harness. I haven't looked at that section of the > code in quite some time and honest

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

Hi Shlomi, My definitive answer would be to say "work with Leon" on this :) He's taken over maintenance on TAP::Harness. I haven't looked at that section of the code in quite some time and honestly, I don't have the time/energy to do so right now.   Best, Ovid -

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

to the relevant > > part > > of TAP::Harness? Seems like I can only set up a single subclass of the > > relevant > > parts in each plugin (like for the formatter or whatever). Or am I missing > > something? > > > > I'm asking because with Test::Run, I can s

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

On Fri, Sep 20, 2013 at 8:29 PM, Shlomi Fish wrote: > I read that post and have one question: can I easily create several > specialised > plugins and have them all apply their modified behaviours to the relevant > part > of TAP::Harness? Seems like I can only set up a single

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

Hi all, On Fri, 20 Sep 2013 21:29:02 +0300 Shlomi Fish wrote: > Hi Ovid, > > On Sat, 7 Sep 2013 14:16:08 -0700 (PDT) > Ovid wrote: > > > Here's a complete example of a TAP::Harness plugin to create a red/green > > progress bar. > > > > htt

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

lugins and have them all apply their modified behaviours to the > relevant part of TAP::Harness? Seems like I can only set up a single subclass > of the relevant parts in each plugin (like for the formatter or whatever). Or > am I missing something? > > I'm asking because with

Re: TAP::Harness and -w

On Sat, Sep 21, 2013 at 6:19 AM, Ricardo Signes wrote: > * Leon Timmermans [2013-09-17T11:26:40] > > Just as I expected, "make it a wiki" means it gets warnocked again. > > > > Can we please make a decision, or if we must first come to an agreement > on > > how to make it? > > Allow me to offer t

Re: TAP::Harness and -w

* Leon Timmermans [2013-09-17T11:26:40] > Just as I expected, "make it a wiki" means it gets warnocked again. > > Can we please make a decision, or if we must first come to an agreement on > how to make it? Allow me to offer this: https://github.com/Perl-Toolchain-Gang/ExtUtils-MakeMaker/pull

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

Hi Ovid, On Sat, 7 Sep 2013 14:16:08 -0700 (PDT) Ovid wrote: > Here's a complete example of a TAP::Harness plugin to create a red/green > progress bar. > > http://blogs.perl.org/users/ovid/2010/05/making-testharness-output-a-progress-bar.html > I read that post and have

Re: TAP::Harness and -w

ntrol - you could get different output from running tests via `prove` than you do via running the test file directly, which could cause you to scrath your head and go "WTF??" I see Ovid mentioned in a later email that prove uses TAP::Harness instead of Test::Harness, implying tha

Re: TAP::Harness and -w

* Leon Timmermans [2013-09-18T19:21:44] > Or both just setting $Test::Harness::switches = ''… Yes. I was cleaning out ~/tmp on the flight over here and I found this dzil plugin: package inc::STFUEUMM; use Moose; extends 'Dist::Zilla::Plugin::MakeMaker'; use namespace::autoclean; afte

Re: TAP::Harness and -w

On Thu, Sep 19, 2013 at 1:17 AM, Ricardo Signes wrote: > It looks like Module::Build already has use_tap_harness. So what's > suggested > is a patch to ExtUtils::MM_Any to switch from Test::Harness to > TAP::Harness...? > Or both just setting $Test::Harness::switches = ''… Leon

Re: TAP::Harness and -w

* Ovid [2013-09-18T04:19:28] > As I said in my previous email on July 7th: backwards-incompatible changes to > the backwards-compatibility layer (Test::Harness) are not a good idea. The > proper response is to have people impacted by this issue switch to > TAP::Harness, as was sugge

Re: TAP::Harness and -w

As I said in my previous email on July 7th: backwards-incompatible changes to the backwards-compatibility layer (Test::Harness) are not a good idea. The proper response is to have people impacted by this issue switch to TAP::Harness, as was suggested several years ago when Test::Harness 3.0 was

Re: TAP::Harness and -w

w to test runs: >- that's how Test::Harness has always worked, ... This really isn't a question of pros/cons of -w. That should be an option for the user with sensible defaults. It already is an option with sensible defaults in TAP::Harness. I believe Test::Harness is a compatib

Re: TAP::Harness and -w

On Tue, Sep 17, 2013 at 7:13 PM, Mark Stosberg wrote: > I think a pro/con list is a reasonable request. I've read all the > messages myself, am a regular user of Perl's testing tools, and the > benefits and drawbacks are not clear to me either. > > An attempting-to-be-neutral summary would be ver

Re: TAP::Harness and -w

of > warnings in dependencies you don't directly control Thank you. I would rather TAP::Harness not enable warnings by default. I would prefer to opt-in, rather than opt out. Mark

Re: Re: TAP::Harness and -w

On Tuesday, September 17, 2013 01:13:26 PM Mark Stosberg wrote: > An attempting-to-be-neutral summary would be very helpful. Pro of adding -w to test runs: - that's how Test::Harness has always worked, and people might be relying on that behavior Cons of adding -w to test runs:

Re: TAP::Harness and -w

On 09/17/2013 11:26 AM, Leon Timmermans wrote: > On Sun, Jul 7, 2013 at 11:45 AM, Ovid > wrote: > > I'm winding up with astonishingly little bandwidth due to launching > our company, so I was hoping to see a strong consensus from the > users. I would

Re: TAP::Harness and -w

On Sun, Jul 7, 2013 at 11:45 AM, Ovid wrote: > I'm winding up with astonishingly little bandwidth due to launching our > company, so I was hoping to see a strong consensus from the users. I would > also love to see examples of where the change or lack thereof is causing an > issue. I am SWAMPED w

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

simply wrap > runtests() in a subclass, process the arguments, and call next::method with > the > modified arguments. > > However, I still don't know how to write a plugin like that exactly (and how > to > get prove to recognise it). This section - > https://metacpa

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

Hi Ovid, On Sat, 7 Sep 2013 14:16:08 -0700 (PDT) Ovid wrote: > Here's a complete example of a TAP::Harness plugin to create a red/green > progress bar. > > http://blogs.perl.org/users/ovid/2010/05/making-testharness-output-a-progress-bar.html Thanks! I'll

Re: How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

Here's a complete example of a TAP::Harness plugin to create a red/green progress bar. http://blogs.perl.org/users/ovid/2010/05/making-testharness-output-a-progress-bar.html Cheers, Ovid   -- IT consulting, training, international recruiting        http://www.allaroundtheworld.fr/. Buy my

How to Port https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames to TAP::Harness

Hi all, I'd like to know what is the best way to create a plugin for https://metacpan.org/module/TAP::Harness which will behave similarly to https://metacpan.org/module/Test::Run::Plugin::TrimDisplayedFilenames . I found out that the runtests method can accept aliases to be displayed inste

Re: TAP::Harness and -w

On Sun, Jul 7, 2013 at 6:00 PM, Ovid wrote: > What toolchain software is being impacted by this and how hard would it be to > make the switch? AFAIK only ExtUtils::MakeMaker and Module::Build use it. The latter can already use TAP::Harness, but there are some details we'd might

Re: TAP::Harness and -w

; laid out. If this is too much, I should turn over maintainership to someone > with > more bandwidth to ensure I'm not a blocker. > > wiki page created: > https://github.com/Perl-Toolchain-Gang/Test-Harness/wiki/TAP::Harness-and--the-w-flag Karen, Thank you for putting t

Re: TAP::Harness and -w

e with > more bandwidth to ensure I'm not a blocker. wiki page created: https://github.com/Perl-Toolchain-Gang/Test-Harness/wiki/TAP::Harness-and--the-w-flag

Re: TAP::Harness and -w

- Original Message - > From: Ricardo Signes > > * Leon Timmermans [2013-07-04T14:04:21] >> By what process? Define consensus? Given Andy is the official >> maintainer and Ovid is the effective maintainer, I don't think they >> need our consensus a priori. > > 06perms.txt says: > >

Re: TAP::Harness and -w

* Eric Wilhelm [2013-07-04T17:33:45] > # from Leon Timmermans on Thursday 04 July 2013: > >> ewilhelm : We should keep the original change, but update EUMM to > >>restore -w > > > >I'm not sure that's what he meant. > > Yeah no. I said get r

Re: TAP::Harness and -w

# from Leon Timmermans on Thursday 04 July 2013: >> ewilhelm : We should keep the original change, but update EUMM to >>restore -w > >I'm not sure that's what he meant. Yeah no. I said get rid of Test::Harness. TAP::Harness provides a cleaner interface and this de

Re: TAP::Harness and -w

* Leon Timmermans [2013-07-04T14:04:21] > By what process? Define consensus? Given Andy is the official > maintainer and Ovid is the effective maintainer, I don't think they > need our consensus a priori. 06perms.txt says: Test::Harness,ANDYA,m Test::Harness,MSCHWERN,c Test::Harness,OVID,c

Re: TAP::Harness and -w

On Tue, Jul 2, 2013 at 8:51 PM, Ricardo Signes wrote: > > I just submitted: > > https://github.com/Perl-Toolchain-Gang/Test-Harness/pull/16 > > ...to document two undocumented changes. First, the removal of "turn on -w by > default with no easy way to turn it off" and secondly the reversion of

TAP::Harness and -w

I just submitted: https://github.com/Perl-Toolchain-Gang/Test-Harness/pull/16 ...to document two undocumented changes. First, the removal of "turn on -w by default with no easy way to turn it off" and secondly the reversion of that. These commits are, respectively: https://github.com/Perl

Re: TAP::Harness uses lots of RAM to store test results

On Thu, Apr 11, 2013 at 10:24:35AM -0700, Buddy Burden wrote: > Nicholas, > > tl;dr: TAP::Harness uses lots of RAM to store test results > > Particularly lots and lots for millions of little "ok\n"s > > It would be nice if it didn't use lots of RAM when sto

Re: TAP::Harness uses lots of RAM to store test results

Nicholas, tl;dr: TAP::Harness uses lots of RAM to store test results > Particularly lots and lots for millions of little "ok\n"s > It would be nice if it didn't use lots of RAM when storing things that > mostly > pass. > Yes, I ran into this before.(*) I was ref

Re: TAP::Harness uses lots of RAM to store test results

> Which makes me wonder - just how much memory is TAP::Parser using. > In particular, is TAP::Parser using the same amount of memory to store 65850 > "ok"s as it would to store some mix of 65850 "ok"s and "not ok"s? > Which I'm starting to think, for large test suites, isn't that efficient. > Most

TAP::Harness uses lots of RAM to store test results

tl;dr: TAP::Harness uses lots of RAM to store test results Particularly lots and lots for millions of little "ok\n"s It would be nice if it didn't use lots of RAM when storing things that mostly pass. So, the long(er) story. I use to be able to build and test blead on my Raspb

Re: Can TAP::Harness::Archive be made to play well with TAP::Parser::Aggregate

This is now available on CPAN: http://search.cpan.org/dist/TAP-Harness-Multiple/ Tested on Linux and Darwin but not yet on Windows. Thank you very much. Jim Keenan

Re: Can TAP::Harness::Archive be made to play well with TAP::Parser::Aggregate

On 10/22/11 12:54 PM, James E Keenan wrote: I have now achieved this in the kid51/testsets2 branch of Parrot. This should yield two new modules for CPAN. Details to come. Development is proceeding here: https://github.com/jkeenan/TAP-Harness-Multiple

Re: Can TAP::Harness::Archive be made to play well with TAP::Parser::Aggregate

On 10/16/11 10:33 PM, James E Keenan wrote: For certain modifications to the Parrot project's smoke testing mechanism, I need to create an archive from an aggregation of test harnesses and then send that archive to our smoke server. Has anyone tried to combine these two modules with good res

Re: Can TAP::Harness::Archive be made to play well with TAP::Parser::Aggregate

ely, I have not figured out how to make TAP::Harness::Archive do this. Here is the code I have so far: Everything seems fine until I get to the very last line. The subroutine send_archive_to_smolder() (which essentially wraps around an LWP::UserAgent call) fails because the archive file 'parrot_test

Can TAP::Harness::Archive be made to play well with TAP::Parser::Aggregate

t;new; $aggregator->start(); foreach my $set (@targets) { # rewrite environment &{$set->{rule}} if defined $set->{rule}; print STDERR "$set->{label}: running with: $ENV{TEST_PROG_ARGS}\n"; my $harness = TAP::Harness->new(

Bug in TAP::Harness::Archive->aggregator_from_archive()

So I think I have found a bug in TAP::Harness::Archive->aggregator_from_archive(). If the archive has a meta.yml file, there's a corner case where files aren't added properly. The code block is lines 340-356: if( -e $yaml_file) { # parse it into a structure

Re: Make TAP::Harness Output Failures Diagnostics?

On Feb 20, 2009, at 12:34 PM, Andy Armstrong wrote: Yeah, I think that's reasonable - although it would be nice at some point to do something about the option proliferation that seems to afflict us. That's not your fault of course :) Thanks. You you should probably subscribe to http://ww

Re: Make TAP::Harness Output Failures Diagnostics?

On Feb 20, 2009, at 12:34 PM, Andy Armstrong wrote: Yeah, I think that's reasonable - although it would be nice at some point to do something about the option proliferation that seems to afflict us. That's not your fault of course :) Thanks. You you should probably subscribe to http://w

Re: Make TAP::Harness Output Failures Diagnostics?

Andy Armstrong wrote: > On 20 Feb 2009, at 16:52, David E. Wheeler wrote: >> On Feb 20, 2009, at 3:18 AM, Andy Armstrong wrote: >> >>> RENUMBER >> >> Won't that fuck up existing users of the library? > > Yeah, I was making a BASIC joke :) A very basic joke. -- 44. I am not the atheist chaplain

Re: Make TAP::Harness Output Failures Diagnostics?

On 20 Feb 2009, at 20:25, David E. Wheeler wrote: Well, almost. I see which test failed, which is a big help, but not any diagnostics. So I think I'll add a `diagnostics` parameter. Make sense? Yeah, I think that's reasonable - although it would be nice at some point to do something about

Re: Make TAP::Harness Output Failures Diagnostics?

On Feb 20, 2009, at 10:20 AM, Andy Armstrong wrote: On 20 Feb 2009, at 16:52, David E. Wheeler wrote: On Feb 20, 2009, at 3:18 AM, Andy Armstrong wrote: RENUMBER Won't that fuck up existing users of the library? Yeah, I was making a BASIC joke :) The description for verbose should really

Re: Make TAP::Harness Output Failures Diagnostics?

On 20 Feb 2009, at 16:52, David E. Wheeler wrote: On Feb 20, 2009, at 3:18 AM, Andy Armstrong wrote: RENUMBER Won't that fuck up existing users of the library? Yeah, I was making a BASIC joke :) The description for verbose should really be "show the raw TAP stream". Patches / commits w

Re: Make TAP::Harness Output Failures Diagnostics?

On Feb 20, 2009, at 3:18 AM, Andy Armstrong wrote: RENUMBER Won't that fuck up existing users of the library? The description for verbose should really be "show the raw TAP stream". Patches / commits welcome - but I'm not going to have time to do anything more than review said patches /

Re: Make TAP::Harness Output Failures Diagnostics?

- Original Message > From: Ovid > > Remember Ovid and I going at it like Godzilla and Rodan over merging STDOUT > > and STDERR when TH3 was being put together? > > Yup. This has bitten me today at work. Badly :( > > All the more reason why we need TB2 to be done today :) You know,

Re: Make TAP::Harness Output Failures Diagnostics?

On 19 Feb 2009, at 21:16, Michael G Schwern wrote: This makes me think that -1 should actually be "normal", from what Schwern has said, and 0 should include the failures and diagnostics and messages and whatnot (# stuff), as Andy seems to have expected in the past. But I can't really figure ou

Re: Make TAP::Harness Output Failures Diagnostics?

On 19 Feb 2009, at 20:01, Michael G Schwern wrote: Andy Armstrong wrote: On 18 Feb 2009, at 22:44, Michael G Schwern wrote: The thing which most takes advantage of this is TODO tests. They send their failure diagnostics to STDOUT so the user is not spammed with passing test information.

Re: Make TAP::Harness Output Failures Diagnostics?

- Original Message > From: Michael G Schwern > > The current behaviour also means that prove's --merge switch hides > > diagnostics: > > Remember Ovid and I going at it like Godzilla and Rodan over merging STDOUT > and STDERR when TH3 was being put together? Yup. This has bitten me t

Re: Make TAP::Harness Output Failures Diagnostics?

On Feb 19, 2009, at 1:16 PM, Michael G Schwern wrote: What prove is referring to in -1 is suppressing its own messages about test failure, not TAP comments. Ah, okay. What you want is a .5 (didn't we figure out in BASIC that you don't closely space your numeric sequences?) which is "show

Re: Make TAP::Harness Output Failures Diagnostics?

David E. Wheeler wrote: > Hrm. Reading the documentation: > > =item * C > > Set the verbosity level: > > 1 verbosePrint individual test results to STDOUT. > 0 normal > -1 quiet Suppress some test output (mostly failures > while tests a

Re: Make TAP::Harness Output Failures Diagnostics?

On Feb 19, 2009, at 10:07 AM, David E. Wheeler wrote: As a way of dealing with the immediate need, I'd love to see a way to just tell TAP::Harness to emit all diagnostics, whether failure diagnostics or freeform output, as you say. It should be off by default, as you pointed out i

Re: Make TAP::Harness Output Failures Diagnostics?

Andy Armstrong wrote: > On 18 Feb 2009, at 22:44, Michael G Schwern wrote: >> The thing which most takes advantage of this is TODO tests. They send >> their >> failure diagnostics to STDOUT so the user is not spammed with passing >> test >> information. > > I didn't know that... > > The current

Re: Make TAP::Harness Output Failures Diagnostics?

at could take a while, and I have a need to see the diagnostics and whatnot now. As I said in a previous message: As a way of dealing with the immediate need, I'd love to see a way to just tell TAP::Harness to emit all diagnostics, whether failure diagnostics or freeform output, as y

Re: Make TAP::Harness Output Failures Diagnostics?

On 18 Feb 2009, at 22:44, Michael G Schwern wrote: The thing which most takes advantage of this is TODO tests. They send their failure diagnostics to STDOUT so the user is not spammed with passing test information. I didn't know that... The current behaviour also means that prove's --merg

Re: Make TAP::Harness Output Failures Diagnostics?

On 18 Feb 2009, at 22:11, David E. Wheeler wrote: Of course if I use -v, it passes `verbosity => 1` to TAP::Harness, but I'd love to be able to see the failure diagnostics without having to see all of the passing test TAP output, too. Is there some way to get TAP::Harness to pass

Re: Make TAP::Harness Output Failures Diagnostics?

to display informative, free-form output to the user. One proposed solution is the TAP logging syntax, but it wasn't discussed at the TAP summit in Oslo last year. It's status is in limbo. http://testanything.org/wiki/index.php/TAP_logging_syntax As a way of dealing with the immedi

Re: Make TAP::Harness Output Failures Diagnostics?

David E. Wheeler wrote: > On Feb 18, 2009, at 2:04 PM, David E. Wheeler wrote: > >> Of course if I use -v, it passes `verbosity => 1` to TAP::Harness, but >> I'd love to be able to see the failure diagnostics without having to >> see all of the passing test TAP o

Re: Make TAP::Harness Output Failures Diagnostics?

On Feb 18, 2009, at 2:04 PM, David E. Wheeler wrote: Of course if I use -v, it passes `verbosity => 1` to TAP::Harness, but I'd love to be able to see the failure diagnostics without having to see all of the passing test TAP output, too. Is there some way to get TAP::Harness

Make TAP::Harness Output Failures Diagnostics?

Howdy, When I run prove/TAP::Harness against a Perl test, I can see failures even when not using verbose mode because, IIRC, that data is sent to STDERR and ignored by TAP::Harness: prove t/base.t t/base1/316 # Failed test '... And now strict is turned on' # at t/base

Re: Silence Command Line in TAP::Harness?

On Aug 21, 2008, at 14:48, Andy Armstrong wrote: There was meant to be a smiley in my response. I was just relieved it wasn't some debug /I'd/ left lying around - so thanks :) :-D Best, David

Re: Silence Command Line in TAP::Harness?

On 21 Aug 2008, at 22:05, David E. Wheeler wrote: print join ' ', @command, $/; Oh Jesus, that was stupid. Must've been debugging and completely forgot about it. Sorry for the noise, and thanks for the prompt reply. There was meant to be a smiley in my response. I was just relieved it

Re: Silence Command Line in TAP::Harness?

On Aug 21, 2008, at 12:09, Andy Armstrong wrote: That's your code, no? From https://svn.kineticode.com/pgtap/tags/rel-0.02/pg_prove push @command, qw( --no-psqlrc --no-align --tuples-only --pset pager= --pset null=[NULL] --set ON_ERROR_ROLLBACK=1

Re: Silence Command Line in TAP::Harness?

On 21 Aug 2008, at 19:54, David E. Wheeler wrote: Is there some way to eliminate that noisy line that shows the command that will be run? That's your code, no? From https://svn.kineticode.com/pgtap/tags/rel-0.02/pg_prove push @command, qw( --no-psqlrc --no-align -

Silence Command Line in TAP::Harness?

Howdy, When I run the pgTAP tests through pg_prove, which uses TAP::Harness, it looks like this: % pg_prove -d try sql/*.sql psql --dbname try --no-psqlrc --no-align --tuples-only --pset pager= --pset null=[NULL] --set ON_ERROR_ROLLBACK=1 --set ON_ERROR_STOP=1 --set QUIET=1

Re: TAP::Harness patches

On 2 Jul 2008, at 21:57, Alex Vandiver wrote: Heya, Attached are a number of small patches for TAP::Harness and associated packages. I'm sending this here, because it's not clear from the documentation where bugs and patches should be sent. The Test::Harness queue cc's a

TAP::Harness patches

Heya, Attached are a number of small patches for TAP::Harness and associated packages. I'm sending this here, because it's not clear from the documentation where bugs and patches should be sent. The Test::Harness queue cc's all of p5p, so I erred away from using that. F

Re: TAP::Harness / CPAN problem

Chris Dolan wrote: On Mar 8, 2008, at 11:59 AM, Andy Armstrong wrote: On 8 Mar 2008, at 17:54, Chris Dolan wrote: Perl 5.8.6 (Apple's dist for OSX 10.4) Test::Harness 3.10 TAP::Harness 0.54 TAP::Parser 0.54 CPAN 1.9205 CPANPLUS 0.82 Yeah, you have a mixture of Test::Harnes

Re: TAP::Harness / CPAN problem

On 8 Mar 2008, at 18:12, Chris Dolan wrote: Yeah, you have a mixture of Test::Harness and TAP::Parser installed. You need to delete those old versions of TAP::Harness and TAP::Parser. TAP::* and Test::Harness should be the same versions. Arg, not again! PREFIX vs. --install_base vs

Re: TAP::Harness / CPAN problem

On Mar 8, 2008, at 11:59 AM, Andy Armstrong wrote: On 8 Mar 2008, at 17:54, Chris Dolan wrote: Perl 5.8.6 (Apple's dist for OSX 10.4) Test::Harness 3.10 TAP::Harness 0.54 TAP::Parser 0.54 CPAN 1.9205 CPANPLUS 0.82 Yeah, you have a mixture of Test::Harness and TAP::P

Re: TAP::Harness / CPAN problem

On 8 Mar 2008, at 17:54, Chris Dolan wrote: Has anyone seen this error? Unknown arguments to TAP::Harness::new (verbosity color) at /Users/ chris/perl/lib/perl5/Test/Harness.pm line 274 It's causing both CPAN and CPANPLUS to fail all installs on my development machine. Web search t

TAP::Harness / CPAN problem

Has anyone seen this error? Unknown arguments to TAP::Harness::new (verbosity color) at /Users/ chris/perl/lib/perl5/Test/Harness.pm line 274 It's causing both CPAN and CPANPLUS to fail all installs on my development machine. Web search turned up only this comment, with no

Re: [ANNOUNCE] TAP::Harness::Archive 0.03

nadim khemir wrote: > On Sunday 16 December 2007 23.29.55 Michael G Schwern wrote: >> nadim khemir wrote: >>> On Saturday 15 December 2007 20.53.30 Michael Peters wrote: >>>> The uploaded file >>>> >>>> TAP-Harness-Archive-0.03.tar.gz >

Re: [ANNOUNCE] TAP::Harness::Archive 0.03

On Sunday 16 December 2007 23.29.55 Michael G Schwern wrote: > nadim khemir wrote: > > On Saturday 15 December 2007 20.53.30 Michael Peters wrote: > >> The uploaded file > >> > >> TAP-Harness-Archive-0.03.tar.gz > >> ... > > > > Nice.

Re: [ANNOUNCE] TAP::Harness::Archive 0.03

nadim khemir wrote: > On Saturday 15 December 2007 20.53.30 Michael Peters wrote: >> The uploaded file >> >> TAP-Harness-Archive-0.03.tar.gz >> ... > > Nice. Now, what do we do with it? You RTFM. http://search.cpan.org/perldoc/TAP::Harness::Archive -- I

Re: [ANNOUNCE] TAP::Harness::Archive 0.03

On Saturday 15 December 2007 20.53.30 Michael Peters wrote: > The uploaded file > > TAP-Harness-Archive-0.03.tar.gz > ... Nice. Now, what do we do with it? Cheers, Nadim.

[ANNOUNCE] TAP::Harness::Archive 0.03

The uploaded file TAP-Harness-Archive-0.03.tar.gz has entered CPAN as file: $CPAN/authors/id/W/WO/WONKO/TAP-Harness-Archive-0.03.tar.gz size: 5995 bytes md5: 5a92a2ae5b43469229a68146703d The biggest change in this release is the removal of Archive::Builder and Archive::Extract

Re: TAP::Harness

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

Re: TAP::Harness

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

Re: TAP::Harness

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

Re: TAP::Harness

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

Re: TAP::Harness

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

Re: TAP::Harness

"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

Re: TAP::Harness

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:

Re: TAP::Harness

* 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

Re: TAP::Harness

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.

Re: TAP::Harness

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

Re: TAP::Harness

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

Re: TAP::Harness

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

Re: TAP::Harness

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

Re: TAP::Harness

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

Re: TAP::Harness

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

  1   2   >