Re: [tap] "ok 1 description" vs "ok 1 - description"

"H.Merijn Brand" <h.m.brand@xs4all.nl> Wed, 04 February 2009 08:07 UTC

Return-Path: <h.m.brand@xs4all.nl>
X-Original-To: tap@core3.amsl.com
Delivered-To: tap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53E983A6B65 for <tap@core3.amsl.com>; Wed, 4 Feb 2009 00:07:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.504
X-Spam-Level:
X-Spam-Status: No, score=-0.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L7PBNG4XHG5Y for <tap@core3.amsl.com>; Wed, 4 Feb 2009 00:07:42 -0800 (PST)
Received: from smtp-vbr4.xs4all.nl (smtp-vbr4.xs4all.nl [194.109.24.24]) by core3.amsl.com (Postfix) with ESMTP id D2C4F3A6991 for <tap@ietf.org>; Wed, 4 Feb 2009 00:07:41 -0800 (PST)
Received: from pc09.procura.nl (procura.xs4all.nl [82.95.216.29]) (authenticated bits=0) by smtp-vbr4.xs4all.nl (8.13.8/8.13.8) with ESMTP id n1487F7q057105 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 4 Feb 2009 09:07:16 +0100 (CET) (envelope-from h.m.brand@xs4all.nl)
Date: Wed, 04 Feb 2009 09:07:14 +0100
From: "H.Merijn Brand" <h.m.brand@xs4all.nl>
To: Michael G Schwern <schwern@pobox.com>
Message-ID: <20090204090714.18bdc1a6@pc09.procura.nl>
In-Reply-To: <49893207.30406@pobox.com>
References: <497A77D0.8070500@pobox.com> <335014.20536.qm@web65715.mail.ac4.yahoo.com> <20090124115427.GC9114@pjcj.net> <87vds4podb.fsf@renormalist.net> <497B8530.4080903@pobox.com> <873aezxgen.fsf@renormalist.net> <4984E18D.7000606@pobox.com> <87tz7fvv0h.fsf@renormalist.net> <49850F8C.4020904@pobox.com> <87eiyhvr4f.fsf@renormalist.net> <49893207.30406@pobox.com>
X-Mailer: Claws Mail 3.7.0 (GTK+ 2.12.0; x86_64-unknown-linux-gnu)
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwEAIAAACI8LKTAAAACXBIWXMAAABIAAAASABGyWs+AAAC JElEQVRo3u2aMY4CMQxFczZ6RItEzRm4DBINDbRUSPRInIRbsNK6+dJfezN4kokn48IaCSjysL8d e9Knoj2fr9f9/gllqQ6U9/vxWK3EdwdIEGjRIVCu18NhuxUfK46SH81+fzrdbuKPx/P5ctHQdAdI TKAgpvV6s9ntBEfXEYSGgMQzIHnuFBBjkshCNJ2KtJZ04hHNAugP8bZr3NIHhbcF0AKoK0CoaHXU LUWBIs1n+jV+Fl8CVqOApEXAwyMO/DSR4XVntoAYDR7eBjQupuYAYTMph8Rj21D4m7MChN02tpqs NSnb/KqU2oHCXu5xDCgflj/RAgBiKBIXnICzAsSjWBsTz5K4/HeXYvb8yK5lY3VGEwPi2aONKT+5 AlcxrTPOwcTiraGRChgMEKJh0bVVifGVTq6qgBiNVl8QE29EsK6VE+YJAOG2wz5AvsqUS6uqgHCA n4NGvBYpnJ64Jgg27sCtxtBk1CJIA4S/GhdWKh07QxUB48jWGhZ4jKamRRr/T8/M0AaEyctry6YB 4dTGj9iWZNs3DahES5kPCJOu0RQbF/fQOBprsB9gaO9JtPDzII9U5ySXX7AnuIt91y54AAW7rPpT LCe5gt3F+CLqr2UarGB3MXvMylWGq4+9RCx3TW1oJq1t3HPQlFs6N1fFNEB4s8dn7Ne7ACSm7TPQ I5quAWmw6qBpulHM33B0Csge4Nd8JTTYG2b1XyRe3lH8x34ABJ6aePuQ2N4AAAAASUVORK5CYII=
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by XS4ALL Virus Scanner
Cc: tap@ietf.org
Subject: Re: [tap] "ok 1 description" vs "ok 1 - description"
X-BeenThere: tap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Test Anything Protocol WG discussions <tap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tap>
List-Post: <mailto:tap@ietf.org>
List-Help: <mailto:tap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tap>, <mailto:tap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Feb 2009 08:07:43 -0000

On Tue, 03 Feb 2009 22:13:27 -0800, Michael G Schwern
<schwern@pobox.com> wrote:

> >> What are you doing with them?
> > 
> > Archiving to track history of testruns and recognize result
> > changes. Probably similar to Smolder, I think, maybe more
> > finegrained. Therefore I care for single tests and their descriptions.
> 
> Looking at it another way, the WORST thing that happens with mixing a legacy
> producer which isn't aware of the dash with a post-spec, dash stripping parser
> is that the description might get interpreted wrong and you can't associate a
> description with it's historical results (though that would indicate that the
> test started using a different producer, which stretching this scenario even
> further).  Since using the description as a unique test ID is already a
> heuristic (something that was discussed in some depth at Oslo) your system
> must already be resistant to this problem.
> 
> Finally, if the parser always strips the optional dash it should always come
> out the same whether the producer uses a leading dash or not EXCEPT for one
> contrived case.  When a description deliberately is supposed to have a leading
> " -".  I can only think of a fairly contrived example, but if you wanted to
> output, say, Morse code "- ... -.-", and your producer doesn't know about the
> optional dash, it would say:

It would be nice to take this example in the docs, but then use

	- .- .--.

:)

-- 
H.Merijn Brand  http://tux.nl      Perl Monger  http://amsterdam.pm.org/
using & porting perl 5.6.2, 5.8.x, 5.10.x, 5.11.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, SuSE 10.1, 10.3, and 11.0, AIX 5.2, and Cygwin.
http://mirrors.develooper.com/hpux/           http://www.test-smoke.org/
http://qa.perl.org      http://www.goldmark.org/jeff/stupid-disclaimers/