Re: [LTP] Test Anything Protocal output

Re: [LTP] Test Anything Protocal output

[Cyril Hrubis]

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

Re: [LTP] Test Anything Protocal output

[Cyril Hrubis]

Hi!
> It looks like it could be changes in lib/tst_res.c line 404 in function tst_print().
> There's other components to TAP but the change above it the biggest I think.

Getting 90% working would be easy enough, the real problem is making it
work for all corner cases, which is the reason I would rather want to do
this for a cleaner code.

> > 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.
> 
> Well, if your re-writing it, than TAP could be added after that. Is this re-write
> a long term thing, or something your planning to complete in the next couple months?

The tst_res.c is one of the last files under the lib/ that hasn't been
cleaned up yet and I certainly want to do that before next release,
which would be in aprox. three months.

-- 
Cyril Hrubis
chrubis@suse.cz

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

Re: [LTP] Test Anything Protocal output

[Cyril Hrubis]

Hi!
> > > Well, if your re-writing it, than TAP could be added after that. Is this re-write
> > > a long term thing, or something your planning to complete in the next couple months?
> > 
> > The tst_res.c is one of the last files under the lib/ that hasn't been
> > cleaned up yet and I certainly want to do that before next release,
> > which would be in aprox. three months.
> 
> Ok, I can wait for that. Are you planning on doing it in steps, or just one big update
> for the file ? I ask only to see if there's something I could look at prior to the final release.

Just now I'm still in the planning and designing phase. I will likely
want to discuss the changes before they get commited to LTP, either as
patches on ML or as separate git repo. We can wire up TAP output at that
point.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
Get real-time metrics from all of your servers, apps and tools
in one place.
SourceForge users - Click here to start your Free Trial of Datadog now!
http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list