TAP docs

2005-02-19 Thread Andy Lester
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 comme

Re: TAP docs

2005-02-19 Thread Andy Lester
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 #

Foreign modules in test scripts?

2005-02-19 Thread Steffen Schwigon
Hi! General testing question: Is it ok for a CPAN module to use other modules from CPAN only for the test scripts (e.g. "Text::Diff")? First, I'm not sure about the usage policy. Maybe it's more common to write tests more "low level". Second, I know there is a "build_requires" option in Build.P

Re: Foreign modules in test scripts?

2005-02-19 Thread Andy Lester
Is it ok for a CPAN module to use other modules from CPAN only for the test scripts (e.g. "Text::Diff")? Yes. See http://phalanx.kwiki.org/index.cgi?StandardDotTFiles for examples of .t files that only run if a certain module is installed. xoxo, Andy -- Andy Lester => [EMAIL PROTECTED] => www.pe

Re: Foreign modules in test scripts?

2005-02-19 Thread Mark Stosberg
On 2005-02-20, Steffen Schwigon <[EMAIL PROTECTED]> wrote: > Hi! > > General testing question: > > Is it ok for a CPAN module to use other modules from CPAN only for the > test scripts (e.g. "Text::Diff")? > > First, I'm not sure about the usage policy. Maybe it's more common to > write tests more

Re: TAP docs

2005-02-19 Thread Andy Lester
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

Re: TAP docs

2005-02-19 Thread Jim Cromie
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.

Re: TAP docs

2005-02-19 Thread Andy Lester
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

Re: TAP docs

2005-02-19 Thread Jason Gessner
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 ...

Re: TAP docs

2005-02-19 Thread Andy Lester
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

Re: TAP docs

2005-02-19 Thread chromatic
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

Re: TAP docs

2005-02-19 Thread Andy Lester
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

Re: TAP docs

2005-02-19 Thread Ian Langworth
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