From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Palethorpe Date: Thu, 17 Sep 2020 11:45:45 +0100 Subject: [LTP] TPASS in new test lib In-Reply-To: <20200916085405.GB4464@yuki.lan> References: <20200916071106.GB1433@dell5510> <20200916085405.GB4464@yuki.lan> Message-ID: <87sgbgy946.fsf@suse.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it Hi, Cyril Hrubis 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.