public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jesse Zhang <sen.zhang@windriver.com>
To: "Björn Stenberg" <bjst@enea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] perl-tests: convert to ptest
Date: Wed, 15 May 2013 15:39:47 +0800	[thread overview]
Message-ID: <51933BC3.5090001@windriver.com> (raw)
In-Reply-To: <20130514125841.GV25918@sestofb10.enea.se>

On 05/14/2013 08:58 PM, Björn Stenberg wrote:
> Jesse Zhang wrote:
>> +++ b/meta/recipes-devtools/perl/perl-5.14.3/run-ptest
>> @@ -0,0 +1,2 @@
>> +#!/bin/sh
>> +cd t && ./TEST
> 
> run-ptest also needs to parse the output and reformat results into the standard ptest/automake format, such as "PASS: foo", "FAIL: foo" and "SKIP: foo".

How verbose should the output be? The TEST script actually does its own
analyzing and summarizing of the test results. Do we want the summary
only or all the details? Do you want the detailed output converted to
ptest format too?

For example,

    # ./TEST 
    t/base/cond....................................................ok
    t/base/if......................................................ok
    t/base/lex.....................................................ok
    t/base/num.....................................................ok

    # ./TEST -v
    t/base/cond....................................................1..4
    ok 1
    ok 2
    ok 3
    ok 4
    ok
    t/base/if......................................................1..2
    ok 1
    ok 2
    ok
    t/base/lex.....................................................1..57
    #1	:x: eq :x:
    ok 1

The output from the actual test case conforms to the TAP format (not
sure about the top-level TEST). If you have an analysis tool, why not
support one more widely used format? I can't see much value in forcing
one format everywhere.

jesse



  reply	other threads:[~2013-05-15  7:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14  7:57 [PATCH 0/1] perl-tests: convert to ptest Jesse Zhang
2013-05-14  7:57 ` [PATCH 1/1] " Jesse Zhang
2013-05-14 12:58   ` Björn Stenberg
2013-05-15  7:39     ` Jesse Zhang [this message]
2013-05-15 11:01       ` Björn Stenberg
  -- strict thread matches above, loose matches on Subject: below --
2013-05-17  5:22 [PATCH v2 0/1] " Jesse Zhang
2013-05-17  5:22 ` [PATCH 1/1] " Jesse Zhang
2013-05-17  9:31   ` Björn Stenberg
2013-05-21  2:43     ` Jesse Zhang
2013-05-21 13:50       ` Björn Stenberg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51933BC3.5090001@windriver.com \
    --to=sen.zhang@windriver.com \
    --cc=bjst@enea.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox