--- Julien Beasley [EMAIL PROTECTED] wrote:
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
Ovid wrote:
If you want things to be *really* easy to run test suites in multiple
languages, do this.
another option is this:
http://people.apache.org/~geoff/test-more-separately.tar.gz
which illustrates how to separate planning, etc in perl but use a
foreign tap producing faile - something
On 9 Mar 2007, at 16:15, Eric Hacker wrote:
I know. It probably isn't hard for a human to figure it out. A TAP
consumer can only really make a best guess though.
It wouldn't be hard to information to the TAP to associate
diagnostics with tests but where would that information come from?
On 3/9/07, Andy Armstrong [EMAIL PROTECTED] wrote:
On 9 Mar 2007, at 13:37, Eric Hacker wrote:
Current TAP diagnostics appear after the the test results in the
standard TAP producers.
D'you mean messages produced with diag() ? They appear in same order
relative to the test results in the TAP
On 3/9/07, Andy Armstrong [EMAIL PROTECTED] wrote:
On 9 Mar 2007, at 16:15, Eric Hacker wrote:
I know. It probably isn't hard for a human to figure it out. A TAP
consumer can only really make a best guess though.
It wouldn't be hard to information to the TAP to associate
diagnostics with
On 9 Mar 2007, at 21:57, Michael G Schwern wrote:
http://perl-qa.yi.org/index.php/TAP_diagnostic_syntax
There's already a proposal for this which nobody's found serious
fault with.
Its, oh, 9 months old now. Its backwards compatible with existing
TAP. It
both solves the problems of
Ovid wrote:
@EXPORT = (
@Test::More::EXPORT,
@Test::Differences::EXPORT,
@Test::Exception::EXPORT,
);
Don't forget @EXPORT_OK
Before I go completely off the handle, I'm going to say this once. Lately
there's been a tremendous amount of discussions about the same old crap over
and over again every few months. The same seemingly good but actually
flawed ideas are proposed, the same arguments are raised and the same
There's a lot of noise and very little signal about TAP lately. Absolutely
no real TAP extensions have been implemented. The TAP document remains in
exactly the same form it was 9 months ago.
http://search.cpan.org/~petdance/TAP-1.00/TAP.pm
We're spinning our wheels and going nowhere.
I'm
chromatic wrote:
On Friday 09 March 2007 14:50, Michael G Schwern wrote:
We can leverage any existing status system we want. HTTP status. Exit
status. Throw them all in! Don't find TAP's existing statuses rich
enough? Add your own extension keys! A particular status code not make
David Golden wrote:
Maybe you want to post the wiki address to remind people? ;-)
Doesn't Google know everything by now?
Ok, http://perl-qa.yi.org/index.php/Main_Page
Julien Beasley wrote:
Well at my last job, we had hundreds of test files.. and most of them were
really fast because we wanted to keep the total time to a minimum. Even
then, it took over five minutes to run all of our tests, and that was
getting to be Too Long. So I could definitely see in a
On Mar 9, 2007, at 5:17 PM, Michael G Schwern wrote:
since. There's mistakes, typos, ommissions, you name it. Work on
it. Put
it on a POD wiki to allow easier collaborative editing. Talk with
Ovid
about where the ambiguities are, he's had to work them out for
TAP::Parser.
Better
--- Michael G Schwern [EMAIL PROTECTED] wrote:
Julien Beasley wrote:
Hi,
I've found that using Test::Files in a test script
changes the output of
TODO tests in Test::Harness.
Here's the problem.
$ perl -wle 'use Test::Files; print
Test::Builder-new-exported_to'
Test::Files
# from Julien Beasley
# on Friday 09 March 2007 03:39 pm:
Thanks Ovid! This may be exactly what I'm looking for (since I'm going
to have tests in libtap and perl). However, and I apologize if I'm
wrong about this, doesn't your proposed solution have to start a new
perl interpreter for every
# from Eric Wilhelm
# on Friday 09 March 2007 06:26 pm:
However, if you feel the need for speed, I *think* you could add
support in runtests for --exec '' to turn into @exec=() rather than
@exec=('').
Darn! That sounded like so much fun. I just couldn't resist.
16 matches
Mail list logo
