Skip Menu |
 

This queue is for tickets about the TAP CPAN distribution.

Report information
The Basics
Id: 94352
Status: open
Priority: 0/
Queue: TAP

People
Owner: Nobody in particular
Requestors: erik.bernoth [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



CC: Andy Lester <andy [...] petdance.com>
MIME-Version: 1.0
In-Reply-To: <20140331135802.GA11767 [...] petdance.com>
X-Spam-Status: No, score=-2.698 tagged_above=-99.9 required=10 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
X-Spam-Flag: NO
References: <CAB46HOmE-MTLDyhD7PgSAgwLC+OQCjhi-YmseY97a53gYvV2_w [...] mail.gmail.com> <20140331135802.GA11767 [...] petdance.com>
Content-Type: multipart/alternative; boundary="001a11c20ce6b627b404f5ed83be"
Message-ID: <CAB46HOkwv1b9BMRhjGbz-b4-b1TvppfgTgook_cyYg8jEGGKGg [...] mail.gmail.com>
X-Received: by 10.60.63.12 with SMTP id c12mr24912087oes.23.1396300372629; Mon, 31 Mar 2014 14:12:52 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at bestpractical.com
X-Spam-Score: -2.698
Received: from localhost (localhost [127.0.0.1]) by hipster.bestpractical.com (Postfix) with ESMTP id 5C7FD240619 for <cpan-bug+tap [...] hipster.bestpractical.com>; Mon, 31 Mar 2014 17:13:02 -0400 (EDT)
Received: from hipster.bestpractical.com ([127.0.0.1]) by localhost (hipster.bestpractical.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vusDonn3WolV for <cpan-bug+tap [...] hipster.bestpractical.com>; Mon, 31 Mar 2014 17:13:00 -0400 (EDT)
Received: from la.mx.develooper.com (x1.develooper.com [207.171.7.70]) by hipster.bestpractical.com (Postfix) with SMTP id 9B6F024060E for <bug-tap [...] rt.cpan.org>; Mon, 31 Mar 2014 17:13:00 -0400 (EDT)
Received: (qmail 30784 invoked by alias); 31 Mar 2014 21:12:59 -0000
Received: from mail-oa0-f54.google.com (HELO mail-oa0-f54.google.com) (209.85.219.54) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Mon, 31 Mar 2014 14:12:56 -0700
Received: by mail-oa0-f54.google.com with SMTP id n16so10159885oag.27 for <bug-tap [...] rt.cpan.org>; Mon, 31 Mar 2014 14:12:52 -0700 (PDT)
Received: by 10.76.82.201 with HTTP; Mon, 31 Mar 2014 14:12:52 -0700 (PDT)
Authentication-Results: hipster.bestpractical.com (amavisd-new); dkim=pass header.i= [...] gmail.com
Delivered-To: cpan-bug+tap [...] hipster.bestpractical.com
Subject: Fwd: TAP Specification: How to specify a PLAN line for one test?
Return-Path: <erik.bernoth [...] gmail.com>
X-RT-Mail-Extension: tap
X-Original-To: cpan-bug+tap [...] hipster.bestpractical.com
X-Spam-Check-BY: la.mx.develooper.com
Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LpxDZWXfU+eK0NXy8Pd4x+dWUgQeulccAUPnut4Q36U=; b=yj4UV85N2/7kaiyB/YQtiw4kTSE5Zc+dnn1DsyLF9aKX+xXtglB6YlMPEGskaXJnpp nN1WGO53+o7Sqc9RpSJBr/7F8WKyxIEq17GzZ9PIsuZ3BHbIe1l/iawppspFMiTcJWw8 2QJZ+ix5gmZotxU7iCjB7yxJV5UPRBVGcozywIXUcaGPA338z7Tw2pZvVwzfNuEStLIg 1XfQtA6UMu/YP3yjv9QkAINM+y+h7lYBfmYbmSJDXq/qXQyZgY78ADMv3Bj/p+aqWxMR yVlOMYO0UHBf/A91pGWOwCa0wDER7IRi5TEN3KkzuxLM+qhVWeqUYkyZugzRsEd1i4Ru j01g==
Date: Mon, 31 Mar 2014 23:12:52 +0200
X-Spam-Level:
To: bug-tap [...] rt.cpan.org
From: Erik Bernoth <erik.bernoth [...] gmail.com>
X-RT-Interface: Email
Content-Length: 0
content-type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Content-Length: 1655
Download (untitled) / with headers
text/plain 1.6k
Dear TAP Maintainers, thanks to Andy Lester I was informed that Wikipedia's article on TAP still links to an old version of the specification. Please change that if possible (see forwarded part of this mail). The reason I've written Andy in the first place was that I wasn't sure which are the official borders of N in the PLAN line `1..N`. Especially for the case that I have one test case I am not sure if it is okay for TAP parsers if I write `1..1`. Because there is one example which writes `1..0` I suppose any positive integer is acceptable, stating it clearly in the specification would still be helpful, though, because then I could be sure that parser writers should consider that point. Please update the subsection "the Plan" accordingly. Thanks for creating and maintaining this specification! It helps a lot in developing useful tools! All the Best Erik Show quoted text
---------- Forwarded message ---------- From: Andy Lester <andy@petdance.com> Date: Mon, Mar 31, 2014 at 3:58 PM Subject: Re: TAP Specification: How to specify a PLAN line for one test? To: Erik Bernoth <erik.bernoth@gmail.com>
> currently I'm rewriting the output of a tool of mine to follow your TAP > specification (read from Wikipedia and here: >
https://metacpan.org/pod/release/PETDANCE/Test-Harness-2.64/lib/Test/Harness/TAP.pod ).
> My tool is ideally always outputting a PLAN line specifiying 1..N tests.
That's pretty old, and I probably ought to delete that Test::Harness after all these years. For everything related to TAP, go to http://testanything.org/ The latest & greatest specification is there. Andy -- Andy Lester => andy@petdance.com => www.petdance.com
content-type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-RT-Original-Encoding: utf-8
Content-Length: 2471
MIME-Version: 1.0
In-Reply-To: <CAB46HOkwv1b9BMRhjGbz-b4-b1TvppfgTgook_cyYg8jEGGKGg [...] mail.gmail.com>
X-Mailer: MIME-tools 5.504 (Entity 5.504)
Content-Disposition: inline
X-RT-Interface: Web
References: <CAB46HOmE-MTLDyhD7PgSAgwLC+OQCjhi-YmseY97a53gYvV2_w [...] mail.gmail.com> <20140331135802.GA11767 [...] petdance.com> <CAB46HOkwv1b9BMRhjGbz-b4-b1TvppfgTgook_cyYg8jEGGKGg [...] mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.0.18-6677-1396369770-61.94352-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 2069
It would be helpful to get testanything.com back online, as that contains a lot of great information. A plan for just one test is legal, and '1..1' is the way to declare it: perl -MTest::More -we'plan tests => 1; pass' prints: 1..1 ok 1 On 2014-03-31 14:13:03, erik.bernoth@gmail.com wrote: Show quoted text
> Dear TAP Maintainers, > > thanks to Andy Lester I was informed that Wikipedia's article on TAP > still > links to an old version of the specification. Please change that if > possible (see forwarded part of this mail). > > The reason I've written Andy in the first place was that I wasn't sure > which are the official borders of N in the PLAN line `1..N`. > Especially for > the case that I have one test case I am not sure if it is okay for TAP > parsers if I write `1..1`. Because there is one example which writes > `1..0` > I suppose any positive integer is acceptable, stating it clearly in > the > specification would still be helpful, though, because then I could be > sure > that parser writers should consider that point. Please update the > subsection "the Plan" accordingly. > > Thanks for creating and maintaining this specification! It helps a lot > in > developing useful tools! > > All the Best > Erik > > ---------- Forwarded message ---------- > From: Andy Lester <andy@petdance.com> > Date: Mon, Mar 31, 2014 at 3:58 PM > Subject: Re: TAP Specification: How to specify a PLAN line for one > test? > To: Erik Bernoth <erik.bernoth@gmail.com> > >
> > currently I'm rewriting the output of a tool of mine to follow your > > TAP > > specification (read from Wikipedia and here: > >
> https://metacpan.org/pod/release/PETDANCE/Test-Harness- > 2.64/lib/Test/Harness/TAP.pod > ).
> > My tool is ideally always outputting a PLAN line specifiying 1..N > > tests.
> > That's pretty old, and I probably ought to delete that Test::Harness > after all these years. > > For everything related to TAP, go to http://testanything.org/ The > latest & greatest specification is there. > > Andy > > -- > Andy Lester => andy@petdance.com => www.petdance.com


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.