Skip Menu |

This queue is for tickets about the Test-Harness CPAN distribution.

Report information
The Basics
Id: 29633
Status: rejected
Priority: 0/
Queue: Test-Harness

People
Owner: andy [...] hexten.net
Requestors: MTHURN [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 2.99_02
Fixed in: (no value)



Subject: wishlist: new feature SKIP_OUT
I suggest a new feature tentatively called SKIP_OUT. It would behave like BAIL_OUT in that it stops execution of all tests, but rather than implying failure, SKIP_OUT implies success. (In other words, SKIP_OUT should report all test results obtained so far, but skip all remaining tests.) -- - - Martin 'Kingpin' Thurn
Do you have a use case for that? I'm having a tough time seeing how it'd be useful.
Subject: RE: [rt.cpan.org #29633] wishlist: new feature SKIP_OUT
Date: Wed, 31 Oct 2007 17:40:11 -0400
To: <bug-Test-Harness [...] rt.cpan.org>, <MTHURN [...] cpan.org>
From: "Martin Thurn" <mthurn [...] verizon.net>
Yes. Our module (Tk::Wizard) is a GUI library, if there is no DISPLAY on the test machine, then there's no need in running the vast majority of our tests. (Right now we test for display-ability at the top of EVERY .t file). If we could SKIP_OUT, we could put our few non-GUI tests into one .t file and skip all the rest without failure. - - Martin Show quoted text
> -----Original Message----- > From: Andy Armstrong via RT [mailto:bug-Test-Harness@rt.cpan.org] > Sent: Wednesday, October 31, 2007 13:21 > To: MTHURN@cpan.org > Subject: [rt.cpan.org #29633] wishlist: new feature SKIP_OUT > > > <URL: http://rt.cpan.org/Ticket/Display.html?id=29633 > > > Do you have a use case for that? I'm having a tough time > seeing how it'd be useful. >
On Wed Oct 31 17:40:49 2007, mthurn@verizon.net wrote: Show quoted text
> Yes. Our module (Tk::Wizard) is a GUI library, if there is no DISPLAY > on the test machine, then there's no need in running the vast > majority of our tests. (Right now we test for display-ability at > the top of EVERY .t file). If we could SKIP_OUT, we could put our > few non-GUI tests into one .t file and skip all the rest without > failure.
OK, I can see how that would be useful - but I'm concerned that it might be rather specific to your case. I'm proposing something a little more general: http://testanything.org/pipermail/tap-l/2007-October/000095.html What do you think?
On Wed Oct 31 19:57:06 2007, ANDYA wrote: Show quoted text
And here's a proposal for TSP: http://testanything.org/wiki/index.php/TSP_Test_Steering_Protocol So you'd have a controller test that determined which other tests should run and then output the appropriate TSP. Would that work for you?
On Wed Oct 31 19:57:06 2007, ANDYA wrote: Show quoted text
And here's a proposal for TSP: http://testanything.org/wiki/index.php/TSP_Test_Steering_Protocol So you'd have a controller test that determined which other tests should run and then output the appropriate TSP. Would that work for you?
Subject: RE: [rt.cpan.org #29633] wishlist: new feature SKIP_OUT
Date: Thu, 01 Nov 2007 07:58:41 -0400
To: <bug-Test-Harness [...] rt.cpan.org>, <MTHURN [...] cpan.org>
From: "Martin Thurn" <mthurn [...] verizon.net>
Will TSP allow wildcards, so we could say include "xt/nogui/*.t" exclude "xt/gui/*.t" ? And what exactly will this look like for the "end user" -- the Module author who only knows how to use Test::More? (Is there a TAP For Dummies article out there somewhere? Or do you envision this functionality getting wrapped into an easy-to-use Test:: module?) - - Martin
On Thu Nov 01 07:59:38 2007, mthurn@verizon.net wrote: Show quoted text
> Will TSP allow wildcards, so we could say > > include "xt/nogui/*.t" > exclude "xt/gui/*.t" > > ? And what exactly will this look like for the "end user" -- the > Module author who only knows how to use Test::More? (Is there a > TAP For Dummies article out there somewhere? Or do you envision > this functionality getting wrapped into an easy-to-use Test:: > module?)
Nothing's final - but yes, I'd imagine it'd be wrapped in a module and support wildcards.