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
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: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
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 e
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
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 pla
On Mon, Feb 21, 2005 at 02:42:49PM -, Clayton, Nik wrote:
> T::H specific, not relevant to TAP.
As T::H is the only complete implementation of TAP and thus is something of
a working reference, it is quite relevant to note where it strays from the
ideal.
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 wi
> 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 T
As we don't have a copy of POSIX 1003.3 I don't know if we can really
say
I'm not particularly interested in the POSIX stuff. Seems pretty YAGNI
to me.
Instead of just having a POSIX non-compliance section it might be
worthwhile
having a comparision to other testing systems section, including
"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 dea
@ Test number
1..6
not ok
ok
not ok
ok
ok
will generate
FAILED tests 1, 3, 6
Would it be possible (useful?) to refine this to
FAILED tests 1, 3
MISSING tests 6
Yes, it would be nice for T::H to report missing tests as missing,
instead of failed. Right now, howe
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; http://www.gnu.org/software/dejag
> 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.
"Descrip
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 sho
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
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 te
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
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
On Sat, 2005-02-19 at 20:53 -0600, Jason Gessner wrote:
> is skip supposed to be case sensitive? is it Skip, skip or SKIP ?
>
> TODO seems to be all caps.
T::H doesn't really care, but the documentation could be a little
stricter than the practice.
Aside from that, I also noticed lots of passi
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
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 ...
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 a
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.
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
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
#
26 matches
Mail list logo
