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 _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core