[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tsp-devel] A test campaign manager for dtest
From: |
Frederik Deweerdt |
Subject: |
Re: [Tsp-devel] A test campaign manager for dtest |
Date: |
Mon, 21 Apr 2008 21:58:18 +0200 |
User-agent: |
Mutt/1.5.17 (2007-11-01) |
On Sun, Apr 20, 2008 at 02:26:49PM +0200, Eric Noulard wrote:
[...]
Just finished reading the research paper :).
> Practically TAP only gives us vision of the "ok" steps,
> I want to be able to trace ALL steps: ok, barrier, expect, send, ....
> As an example I may want to define something like an "observer step"
> which may gives me [non-intrusively] state values/counters from a
> running DTester,
> using these values I may implement an ok step in order to validate the range
> of the values.
Ok, I see. Didier seems to prefer a more versatile interface too.
Just for arguments's sake, couldn't that be run like this:
Client -------------- Server
\ / \------ Invariant observer
TAP TAP |
\-> DTestMaster <---TAP--/
Even though what the observer observes is more than simple Ok/Nok steps.
The answer to "did we perform y before x" is still Ok/Nok.
I've got no strong feelings to keep TAP, I just want to make sure that
we're not over engineering here.
[...]
> So DTester do not produce TAP output they produce _part of_ TAP
> output. For exemple when the TAP plan in announced
> 1..N
> at the beginning of the sequence
> the N is computed using the sum of all ok steps from all DTesters
> registered into the DTestMaster.
>
> look at the DTestMaster::run method code.
OK thanks for the clarification, I was mistaken on this.
Regards,
Frederik
Re: [Tsp-devel] A test campaign manager for dtest, T. Decherf, 2008/04/14