On 23 August 2012 15:19, Björn Stenberg <b...@enea.com> wrote:
> And it sometimes
> requires patching and/or translation of the test output to produce a
> generic output format that can be automatically parsed. I have included
> an example patch for bash that does just that.
What is this generic output format? From your patch to bash I suspect
it's at least inspired by the automake "make check" output.
FWIW, this is what "make check" on librest (the first package I had to
hand) gives:
...
make check-TESTS
make[2]: Entering directory `/home/ross/Programming/cvs/librest/tests'
PASS: proxy
PASS: proxy-continuous
PASS: threaded
PASS: oauth
PASS: oauth-async
PASS: oauth2
PASS: flickr
PASS: lastfm
** (process:1267): ERROR **: Generated output for parsed XML does not match:
in: <node0 a00='v00' a01='v01'><node1 a10='v10'></node1><node1
a10='v10'></node1>Cont0</node0>
out: <node0 a01='v01' a00='v00'><node1 a10='v10'></node1><node1
a10='v10'></node1>Cont0</node0>
/bin/sh: line 5: 1267 Trace/breakpoint trap (core dumped) ${dir}$tst
XFAIL: xml
PASS: custom-serialize
=====================================================
All 10 tests behaved as expected (1 expected failure)
=====================================================
make[2]: Leaving directory `/home/ross/Programming/cvs/librest/tests'
...
Would this test suite just work if packaged as ptests?
Ross
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
