Date: Mon, 31 Aug 2015 12:22:44 +0200
From: Cyril Hrubis <chrubis@suse.cz>
Message-ID: <20150831102243.GA17387@rei.suse.cz>
References: <20150829232628.GA14374@fifo99.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <20150829232628.GA14374@fifo99.com>
Subject: Re: [LTP] Test Anything Protocal output
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ltp-list-bounces@lists.sourceforge.net
To: dwalker@fifo99.com
Cc: ltp-list@lists.sourceforge.net

Hi!
> I read your January 2015 article where someone asked if TAP test output would be supported. It sounded like
> you were going to look into it. Did you make any progress?

Unfortunately not yet.

> The reason I asked if because I was wanting the same feature and I was going to review the LTP code to see
> how hard it would be to add it, but I wouldn't want to start if someone else has already done it. I did
> see anything in the git history tho.

Well, have a look at lib/tst_res.c, that is the place where test results
are stored/printed. Unfortunately this code hasn't been cleaned up yet.

I've started to work on this just recently. Just now I'm experimenting
with rewriting it from scratch keeping most of the API unchanged (since
we cannot change easily the API for > ~1000 testcases).

Then there is another problem, so far LTP testcases are executed using
the ltp-pan test driver, which executes testcases, catches segfaults,
etc. We would have to consider how that would interact with the output
generated from testcases.

One option would be to get rid of most of the pan functionality by
moving the test driver code into the test library, so that each testcase
would fork first, then run the real test in it's own virtual terminal,
etc.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list