On Tuesday 15 January 2008 05:13:38 Ovid wrote:
> Why the hell is everyone giving imacat a hard time about this? That's
> just plain mean :(
The dependencies I list for my distributions are not suggestions. Without
those dependencies, my code won't work.
Testing my code without installing tho
--- John Peacock <[EMAIL PROTECTED]> wrote:
> There is a valid reason to perform competely 'tabula rasa' testing,
> where the
> only things installed are the base packages. It's for testing
> upgrading the
> infrastructure modules themselves (see above).
That does not mean it's the only reason f
Hi, you're getting this mail because your CPAN distribution makes use of
Test::Harness::Straps (or you're subscribed to perl-qa).
Test::Harness version 3 will not include Test::Harness::Straps. It was an
experiment, it didn't work out. Sorry. Current users of Straps are
encour
Andy Armstrong wrote:
> On 16 Oct 2007, at 20:04, Michael G Schwern wrote:
>> If somebody REALLY cares they can gut it to use TAP::Parser so it gets
>> future
>> bug and feature fixes. But that's like putting rocket engines on a
>> blimp.
>
> To be honest when I started working on Test::Harness 2
On 16 Oct 2007, at 20:29, Ovid wrote:
Seriously, is there a deprecation plan?
We could just let Adam Kennedy write the test suite :)
http://use.perl.org/~Alias/journal/34680
Woo! That's a doozy. Is Adam here? I think some sort of award may be
in order.
--
Andy Armstrong, Hexten
On 16 Oct 2007, at 20:27, Michael G Schwern wrote:
Because I enjoy calamity as much as the next person, and because
you have too
much Test::Harness stuff to do already, I'll shove out a Straps
release just
to kill this problem for the time being and all CPAN authors to begin
transitioning.
--- chromatic <[EMAIL PROTECTED]> wrote:
> Seriously, is there a deprecation plan?
We could just let Adam Kennedy write the test suite :)
http://use.perl.org/~Alias/journal/34680
(Kidding!)
Cheers,
Ovid
--
Buy the book - http://www.oreilly.com/catalog/perlhks/
Perl and CGI - http://users.
On 16 Oct 2007, at 20:04, Michael G Schwern wrote:
If somebody REALLY cares they can gut it to use TAP::Parser so it
gets future
bug and feature fixes. But that's like putting rocket engines on a
blimp.
To be honest when I started working on Test::Harness 2.xx
compatibility I assumed I'd
chromatic wrote:
> On Tuesday 16 October 2007 05:18:40 Michael G Schwern wrote:
>
>> Honestly, just convert to TAP::Parser. Straps has no future.
>
> It has a zombie future. You can't remove it for TEN YEARS because it's in
> the
> core and people with government contracts rely on it.
Page o
On 16 Oct 2007, at 17:11, chromatic wrote:
On Tuesday 16 October 2007 05:18:40 Michael G Schwern wrote:
Honestly, just convert to TAP::Parser. Straps has no future.
It has a zombie future. You can't remove it for TEN YEARS because
it's in the
core and people with government contracts rel
On Tuesday 16 October 2007 05:18:40 Michael G Schwern wrote:
> Honestly, just convert to TAP::Parser. Straps has no future.
It has a zombie future. You can't remove it for TEN YEARS because it's in the
core and people with government contracts rely on it.
Seriously, is there a deprecation pla
--- Michael G Schwern <[EMAIL PROTECTED]> wrote:
> Also, using a little known feature of Perl, you can get Test::Harness
> 2 to do
> this without any modification. Just say "#!/usr/bin/php" or
> "#!/usr/bin/env
> php" or whatever on the #! line of the test and Perl will honor it
> and run the pro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael G Schwern a écrit :
>
> Also, using a little known feature of Perl, you can get
Test::Harness 2 to do
> this without any modification. Just say "#!/usr/bin/php" or
"#!/usr/bin/env
> php" or whatever on the #! line of the test and Perl will hon
Geoffrey Young wrote:
>> Honestly, just convert to TAP::Parser. Straps has no future.
>
> Apache-Test subclasses Straps to override _command_line() and provide
> php as the test caller (so you can run t/foo.php with php instead of perl).
>
> unfortunately for us, the magic required for this to w
> Honestly, just convert to TAP::Parser. Straps has no future.
Apache-Test subclasses Straps to override _command_line() and provide
php as the test caller (so you can run t/foo.php with php instead of perl).
unfortunately for us, the magic required for this to work with Straps
isn't straightfo
break Straps.
>
> "not break" in what sense? From my reading, Test::Harness::Straps only
> operates by way of Test::Harness dispatching all work through it.
Straps does not depend on Test::Harness, it is the other way around. Straps
can be used independently. That's just
hat sense? From my reading, Test::Harness::Straps only
operates by way of Test::Harness dispatching all work through it.
Since Test::Harness 3.0 will not do this, Test::Harness::Straps will
be "not used" and therefore code relying on it will "not work", when
Test::Harness->V
Andy Lester wrote:
> On Fri, Oct 05, 2007 at 11:22:57AM -0500, brian d foy ([EMAIL PROTECTED])
> wrote:
>> Do you mean that Test::Harness 3.0 won't have it but it will still be
>> there in earlier releases, or that you're going to remove any trace of
>> it from CPAN so it looks like it never exist
On Fri, Oct 05, 2007 at 11:22:57AM -0500, brian d foy ([EMAIL PROTECTED]) wrote:
> Do you mean that Test::Harness 3.0 won't have it but it will still be
> there in earlier releases, or that you're going to remove any trace of
> it from CPAN so it looks like it never existed?
We're not going to ret
In article <[EMAIL PROTECTED]>, Ovid
<[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm sure that many of you are aware of this, but I wanted to remind you
> that with the upcoming release of Test::Harness 3.0,
> Test::Harness::Straps is going away.
Do you mean that
Hi all,
I'm sure that many of you are aware of this, but I wanted to remind you
that with the upcoming release of Test::Harness 3.0,
Test::Harness::Straps is going away. Also posted (with workaround
info) at:
http://www.perlmonks.org/?node_id=642861
http://use.perl.org/~Ovid/journal/
I was building a custom test harness and wanted to capture diagnostic
messages produced by a few venerable Test::* modules. Unfortunately
Test::Harness::Straps redirects only reads from stdout when capturing
the output of .t files.
- As far as I can tell, Test::* modules send diagnostic info
separates pass/fail todo tests any
less than it separates pass/fail todo tests:
ok 1
not ok 2
ok 3 # TODO
not ok 4 # TODO
so if you're splitting one up it seems sensible to split both
Now that you mention it, reporting unexpected successes might be
worthwhile -- but then again, Test::H
On Sat, 2005-07-30 at 11:50 +0100, Adrian Howard wrote:
> I took chromatic to mean that he'd like the test harness to do the
> decorating...
Yep -- that way you don't have to munge whatever formatting
Test::Harness::Straps does, you just decorate on a method that does the
fo
test, not just those that happen to use Test::Builder.
This also coincides with the premise that Test::Harness::Straps are
just
parsing TAP from any given source.
I took chromatic to mean that he'd like the test harness to do the
decorating... so you could do something along the lin
se quite happily.
By the way, Test::TAP::Model is a hack on top of
Test::Harness::Straps that is supposed to make the "toddling off"
part easier.
I hope that in future incarnations (that is Perl 6 land)
Test::Harness::Straps will resemble a SAX like parser, and Test::TAP
will be one ha
use Test::Builder.
This also coincides with the premise that Test::Harness::Straps are just
parsing TAP from any given source.
xoxo,
Andy
--
Andy Lester => [EMAIL PROTECTED] => www.petdance.com => AIM:petdance
On Fri, 2005-07-29 at 15:57 -0700, Michael G Schwern wrote:
> This is, IMHO, the wrong place to do it. The test should not be
> responsible for decorating results, Test::Harness should be.
I also meant in Test::Harness.
-- c
hor didn't think to display it how you like you're screwed.
That said, the idea is to reduce Test::Harness::runtests() to this.
my $strap = Test::Harness::Straps->new;
$strap->decorator(Test::Harness::Decorator::Default->new);
$strap->analyze_file($_)
On Fri, 2005-07-29 at 22:27 +0100, Adrian Howard wrote:
> However, munging together my own command together with various
> _private looking methods to pass to IPC::Run3 and then poking around
> in a results hash all seems a little gnarly.
Only a little? I might have to apply the cluestick wi
Earlier today chromatic kindly gave me a gentle tap with the
cluestick which let me figure out how to give T::H::S STDERR &
STDOUT, which means my mates test results are now toddling off to a
SQLite database quite happily.
However, munging together my own command together with various
_pr
#x27;at line 10 TODO?!)',
+ type => 'todo'
+ },
+ {
+ 'ok' => 1,
+ actual_ok => 1,
+ },
+ {
+ 'ok' => 1,
+ actual_ok => 0,
+ extra => "Test 4 got: '0' (t/todo.
--- chromatic <[EMAIL PROTECTED]> wrote:
> On Wed, 2005-01-26 at 18:51 -0800, Ovid wrote:
> Odd. I think the problem was in looking for undefined values; at
> least,
> I remember ending up with that while writing the patch and running
> the
> Test::Harness tests.
Perhaps we have something else di
On Wed, 2005-01-26 at 18:51 -0800, Ovid wrote:
> This line:
>
> > +elsif ($result{number} and my $extra = $self->_is_extra_line(
> > $line ))
>
> Always fails to collect the data I need because $result{number} is
> false when the extra data is being accumulated. Thus, I changed it to:
>
>
--- Ovid <[EMAIL PROTECTED]> wrote:
> > +elsif ($result{number} and my $extra = $self->_is_extra_line(
> > $line ))
>
> Always fails to collect the data I need because $result{number} is
> false when the extra data is being accumulated. Thus, I changed it
> to:
>
> elsif (!$result{number}
--- chromatic <[EMAIL PROTECTED]> wrote:
> (and displaying better diagnostics on success or failure), here's a
> small patch to Test::Harness::Straps to collect the diagnostic
> information currently dumped to STDERR and to store it in the test
> data structure for Straps u
Hi all,
As threatened in comments on Ovid's journal about colorizing test output
(and displaying better diagnostics on success or failure), here's a
small patch to Test::Harness::Straps to collect the diagnostic
information currently dumped to STDERR and to store it in the test data
str
On Jan 26, 2005, at 5:12p, Andy Lester wrote:
I would love to hear your thoughts and ideas on structures of results.
Here's approximately what I'd like, which could easily be passed to a
template. This is just a brain dump, feel free to tear it apart. A few
of the values are provided for convenie
Hi,
First, thanks for your QA job !
Next, I ask you an advice for Test::Harness::Straps.
(project /1) I today use a lot of script that use Test::More methods.
I run them from several ways: from cron or from cgi.
I use my own function to parse result, and display them as I want.
Yesterday (project
I want to finish the Test::Harness::Straps interface so its usable.
But I can't finish it until people play with it some and I get some
feedback. But people won't use it until its usable. Wash, rinse,
repeat.
To break the loop I've added some new experimental, undocumented
f
http://www.pobox.com/~schwern/src/Test-Harness-2.01.tar.gz
Test::Harness 2.00 didn't cause any disasters (people are actually
using it, right?) so here's 2.01.
2.01 Thu Dec 27 18:54:36 EST 2001
* Added 'passing' to the results to tell you if the test passed
*
Forgot to mention, there are a few user visable interface changes to
Test::Harness::Straps in 2.00_03 (and thus _04) that have changed
since 2.00_01.
* 'summary' is now 'details'. It wasn't much of a summary.
* Test #1 is now element 0 on the details ar
On Thu, Sep 20, 2001 at 02:52:20PM -0400, Shane Landrum wrote:
> My cursory look at CPAN::Smoke says that it's sort of what I want.
> Except that I don't want to have to rely on having a CPAN mirror
Look at CPAN::Smoke::Module and CPAN::Smoke::Author to set up modules
without a CPAN index.
> I
On Thu, Sep 20, 2001 at 11:56:57AM -0400, Michael G Schwern ([EMAIL PROTECTED]) wrote:
>
> Ok, I'll have to trap STDERR. It's going to be tricky to preserve the
> interweaving of STDOUT and STDERR though, and to do it without
> IPC::Open3.
Thanks. In the meantime, I'll see what I can do as a us
From: Kirrily Robert [[EMAIL PROTECTED]]
> In perl.qa, Schwern wrote:
> > Hmmm, more people trying it, really, especially on the weird
> > platforms. I rewrote all the test analysis logic and I
> > still afraid I broke something.
> We're probably going to start using it for e-smith's testing fo
On Thu, Sep 20, 2001 at 12:17:08PM -0400, Kirrily Robert wrote:
> We're probably going to start using it for e-smith's testing foo.
> I've dinked around with it briefly, enough to know that it does roughly
> what I want, but I'm not on any kind of unusual platform or anything, so
> I don't know if
In perl.qa, you wrote:
>On Thu, Sep 20, 2001 at 10:35:49AM -0400, Shane Landrum wrote:
>> So, I've just found Test::Harness::Straps--- thanks to Skud
>> for pointing me in the right direction. Anyone else using it?
>> I'm working on using it to write a web-based
On Thu, Sep 20, 2001 at 11:30:38AM -0400, Shane Landrum wrote:
> I want T::H::Straps to be able to tell me whether there were warnings
> during my test run, and if so, what they were. Working modules
> don't generally warn. Perhaps that should be switchable.
Ok, I'll have to trap STDERR. It's
On Thu, Sep 20, 2001 at 10:58:08AM -0400, Michael G Schwern ([EMAIL PROTECTED]) wrote:
>
> Hmmm, more people trying it, really, especially on the weird
> platforms. I rewrote all the test analysis logic and I still afraid I
> broke something.
>
> The interface needs to be gelled a bit. Half of
On Thu, Sep 20, 2001 at 10:35:49AM -0400, Shane Landrum wrote:
> So, I've just found Test::Harness::Straps--- thanks to Skud
> for pointing me in the right direction. Anyone else using it?
> I'm working on using it to write a web-based test summarizer
> for my users.
>
So, I've just found Test::Harness::Straps--- thanks to Skud
for pointing me in the right direction. Anyone else using it?
I'm working on using it to write a web-based test summarizer
for my users.
Schwern, do you have plans for releasing T::H 2.00 to CPAN
as anything other than an a
51 matches
Mail list logo
