From: Richard Palethorpe <rpalethorpe@suse.de>
To: ltp@lists.linux.it
Subject: [LTP] TPASS in new test lib
Date: Thu, 17 Sep 2020 11:45:45 +0100 [thread overview]
Message-ID: <87sgbgy946.fsf@suse.de> (raw)
In-Reply-To: <20200916085405.GB4464@yuki.lan>
Hi,
Cyril Hrubis <chrubis@suse.cz> writes:
> Hi!
>> Although leaving this to Cyril (although having T prefix or not is quite
>> cosmetic, he had a reason to omit it). Also there is ongoing rewrite of tests
>> still using legacy API to use new API, thus the inconsistency will disappear in
>> the long term.
>>
>> IMHO: don't care that much about legacy API, but synchronize new C and shell
>> API.
>
> I do not care that much here, but I do not think that we should expect
> exact test output unless we have specified it somewhere.
>
> --
> Cyril Hrubis
> chrubis@suse.cz
It would be possible to output something like TAP and allow it to be set
at compile time.
Infact it should be possible to print JSON, xUnit or whatever
snippets. We could also print the meta data for each test at the
begining which would work quite well with structured formats.
--
Thank you,
Richard.
next prev parent reply other threads:[~2020-09-17 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 20:54 [LTP] TPASS in new test lib Bird, Tim
2020-09-16 4:50 ` Xiao Yang
2020-09-16 7:11 ` Petr Vorel
2020-09-16 8:54 ` Cyril Hrubis
2020-09-16 16:29 ` Bird, Tim
2020-09-17 8:40 ` Cyril Hrubis
2020-09-18 11:45 ` Cyril Hrubis
2020-09-17 10:45 ` Richard Palethorpe [this message]
2020-09-17 11:23 ` Petr Vorel
2020-09-17 11:33 ` Petr Vorel
2020-09-17 12:49 ` Cyril Hrubis
2020-09-16 8:43 ` Cyril Hrubis
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=87sgbgy946.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
/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;
as well as URLs for NNTP newsgroup(s).