Re: [tap] "Nested TAP" in the draft

Ovid <publiustemp-tapx@yahoo.com> Tue, 02 March 2010 17:20 UTC

DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=qiwyio0HQVL5wFJvORyJvj+7R7BE5A8gwuYMkWYXdXAHmxilQSi58dSiFH0nTBZssAiDd/iaD8u59sL7OwRd2dn4RcopAV+YSKb7GkQGaDVMHUt9LsrBaWoKSMyXwvWxV0UGSAiJGFgR9gJ2DABDvVL6cfkaTch37R3+iI9xwAk=;
Message-ID: <91803.89490.qm@web65716.mail.ac4.yahoo.com>
Date: Tue, 02 Mar 2010 09:20:56 -0800
From: Ovid <publiustemp-tapx@yahoo.com>
To: Salve J Nilsen <sjn@pvv.org>
In-Reply-To: <alpine.DEB.1.00.1003021808590.2167@decibel.pvv.ntnu.no>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Cc: TAP <tap@ietf.org>
Subject: Re: [tap] "Nested TAP" in the draft
Precedence: list
Reply-To: publiustemp-tapx@yahoo.com

--- On Tue, 2/3/10, Salve J Nilsen <sjn@pvv.org> wrote:

> From: Salve J Nilsen <sjn@pvv.org>

> Could you remind us a little of what the purpose of Nested
> TAP was?

The main purpose is that it allows multiple TAP streams to be combined into a single stream.  It can be nested to arbitrary depths, but all nesting depths must be consistent.  The first "unindented" line under each nest is the pass/fail status of the nest.  A nest is represented as a single pass/fail result for the outer stream.

  1..3
  ok 1
  ok 2
    ok 1
    not ok 2
    not ok 3
    ok 4
    1..4
  not ok 3 - This summarizes above results

So the outer stream has three tests, one of them being the summary line for the preceding nest.

Also, note that the top-level stream has the plan before, but the nest has the plan after.  Some have found this useful when they want a "subtest" where they don't know how many tests are run, but they still want that leading plan.

Conceptually this maps well to xUnit where a test method is a single test with multiple asserts.  With nested TAP, the nest is equivalent to the asserts and the summary test line is equivalent to the test method.

One unanswered question regarding nested TAP: are skip and todo allowed on summary test lines?

Cheers,
Ovid
--
Buy the book         - http://www.oreilly.com/catalog/perlhks/
Tech blog            - http://use.perl.org/~Ovid/journal/
Twitter              - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6

[tap] Wakey wakey Salve J Nilsen
Re: [tap] Wakey wakey Gaurav Vaidya
Re: [tap] Wakey wakey David E. Wheeler
Re: [tap] Wakey wakey Gaurav Vaidya
Re: [tap] Wakey wakey Salve J Nilsen
Re: [tap] Wakey wakey Ovid
Re: [tap] Wakey wakey Ovid
[tap] Octothorpe/hash "#" in descriptions? Salve J Nilsen
Re: [tap] Wakey wakey Gaurav Vaidya
Re: [tap] Octothorpe/hash "#" in descriptions? Salve J Nilsen
[tap] "Nested TAP" in the draft Salve J Nilsen
[tap] "Left justified" TAP Salve J Nilsen
Re: [tap] "Nested TAP" in the draft Ovid
[tap] Authoritative version of the TAP draft Salve J Nilsen
[tap] TAP MIME type Salve J Nilsen
Re: [tap] "Left justified" TAP Ovid
Re: [tap] "Nested TAP" in the draft Salve J Nilsen
Re: [tap] TAP MIME type Aristotle Pagaltzis
Re: [tap] "Nested TAP" in the draft Aristotle Pagaltzis