Andy Lester [EMAIL PROTECTED] writes:
http://www.petdance.com/random/tap.html
Everyone: I still need more comments. Pete Krawczyk's the only one to
provide complaints yet.
@ Test number
1..6
not ok
ok
not ok
ok
ok
will generate
FAILED tests 1, 3, 6
Would
On Sun, Feb 20, 2005 at 10:19:09AM +0100, Johan Vromans wrote:
http://www.petdance.com/random/tap.html
Everyone: I still need more comments. Pete Krawczyk's the only one to
provide complaints yet.
There's no discussion of the exit code of the test process.
Acknowledgements should
On Sun, Feb 20, 2005 at 10:19:09AM +0100, Johan Vromans wrote:
http://www.petdance.com/random/tap.html
Everyone: I still need more comments. Pete Krawczyk's the only one to
provide complaints yet.
There's no discussion of the exit code of the test process.
Descriptions should
On Mon, Feb 21, 2005 at 12:29:59PM -, Clayton, Nik wrote:
Perhaps a gammar (or just a regex) that describes a fully conforming test
line would be helpful.
Some comments about POSIX (non-)conformance might be useful, see the DejaGnu
docs for examples;
Descriptions should not begin with a digit -- at the moment this
generates
a warning (in Test::* and libtap). It should probably be documented
that
this is a non-fatal error.
I specifically left that out. It's an issue that Test::More deals
with, but doesn't have to. TAP.pod really only
Dejagnu,
POSIX and JUnit, drawing analogies between them and TAP. It would help
those who are already familiar with other systems to more easily
understand
TAP.
This sounds like a separate document for someone to write for us to
include with T::H, but not part of the TAP docs.
--
Andy Lester
I specifically left that out. It's an issue that Test::More deals
with, but doesn't have to. TAP.pod really only deals with
TAP, not the libs that create it.
Sort of.
1. qq{will generate
FAILED tests 1, 3, 6
Failed 3/6 tests, 50.00% okay}
That's T::H output.
2. qq{Currently
On Mon, Feb 21, 2005 at 02:42:49PM -, Clayton, Nik ([EMAIL PROTECTED])
wrote:
1. qq{will generate
FAILED tests 1, 3, 6
Failed 3/6 tests, 50.00% okay}
That's T::H output.
Ok, modified so that it notes that it's T::H output.
2. qq{Currently Test::Harness does nothing with the
In certain instances a test file may not know how many test points
it will ultimately be running. In this case the plan can be the last
non-diagnostic line in the output.
This feature is new to me--and I have to say, it seems nearly useless.
I consider that the primary purpose of a
This feature is new to me--and I have to say, it seems nearly useless.
It's the ages-old argument about the value of the plan. Some people
don't like the plan, and some do.
was expected. I propose to fix this by allowing, in place of a plan at
the beginning, something like the line ends with
On Mon, Feb 21, 2005 at 08:31:43PM -0600, Andy Lester wrote:
This feature is new to me--and I have to say, it seems nearly useless.
It's the ages-old argument about the value of the plan. Some people
don't like the plan, and some do.
I don't mean the plan is new, only the plan at the end.
On Mon, Feb 21, 2005 at 08:31:43PM -0600, Andy Lester wrote:
was expected. I propose to fix this by allowing, in place of a plan at
the beginning, something like the line ends with plan.
In effect, finding
ok 1
as the first line means ends with plan.
I think that's not mentioned
If your tests are numbered then a plan is mandatory. In certain
instances a
test file may not know how many test points it will ultimately be
running.
In this case the plan can be the last non-diagnostic line in the
output.
The plan has to exist, whether it's the first or last line. I've added
On Mon, Feb 21, 2005 at 08:58:46PM -0600, Andy Lester wrote:
The plan has to exist, whether it's the first or last line. I've added
that to the docs.
Ah, that clarifies it. I misunderstood the current situation--I didn't
realize that Test::More automatically adds the plan at the bottom when
I'm updating the TAP docs in Test::Harness, so that I can update
Test::Harness and get it into bleadperl so that (I hope) it makes it
into Perl 5.8.7.
Please have a look at my latest/greatest HTMLified version of
Test::Harness::TAP.pod:
http://www.petdance.com/random/tap.html
Get those
On Sat, Feb 19, 2005 at 10:34:06AM -0600, Andy Lester ([EMAIL PROTECTED]) wrote:
Please have a look at my latest/greatest HTMLified version of
Test::Harness::TAP.pod:
http://www.petdance.com/random/tap.html
Also note that it goes with the form:
ok 1 Description # Directive
#
http://www.petdance.com/random/tap.html
Looks good. Thanks for working on this.
You're welcome.
Everyone: I still need more comments. Pete Krawczyk's the only one to
provide complaints yet.
xoxo,
Andy
--
Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Andy Lester wrote:
http://www.petdance.com/random/tap.html
Looks good. Thanks for working on this.
You're welcome.
Everyone: I still need more comments. Pete Krawczyk's the only one to
provide complaints yet.
The synopsis uses passive voice; . is called TAP.
Id turn that around.
The synopsis uses passive voice; . is called TAP.
Id turn that around.
TAP, the Test Anything Protocol, is .
Fixed, thanks.
Everything else reads fine.
Id like to see Description replaced by Remarks, but maybe that fish is
already fried.
Battered, fried, slathered with tartar sauce
is skip supposed to be case sensitive? is it Skip, skip or SKIP ?
TODO seems to be all caps.
-jason gessner
[EMAIL PROTECTED]
On Feb 19, 2005, at 8:48 PM, Andy Lester wrote:
The synopsis uses passive voice; . is called TAP.
Id turn that around.
TAP, the Test Anything Protocol, is
On Feb 19, 2005, at 8:53 PM, Jason Gessner wrote:
is skip supposed to be case sensitive? is it Skip, skip or SKIP ?
Both TODO and SKIP are case-insensitive. I've updated to make that
explicit.
xoa
--
Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
On Feb 19, 2005, at 8:53 PM, Jason Gessner wrote:
is skip supposed to be case sensitive? is it Skip, skip or SKIP ?
Either way. I've updated it.
xoa
--
Andy Lester = [EMAIL PROTECTED] = www.petdance.com = AIM:petdance
Under TESTS AND PLANS: The plan, the first sentence of the third
paragraph seems to fit better at the end of the previoius paragraph:
This is a safeguard in case your test dies quietly in the middle
of its run. It should be the first non-diagnostic line output by
your test
23 matches
Mail list logo
