catching-up...

["Durand, Jacques R." <JDurand@us.fujitsu.com>]

Trying to catch-up with this week-end outburst...

This is just a summary email, attempting to classify TA -related issues seen on the list, and reorganizing threads on these:

TA thread #1: General anatomy of the TA (will rename the thread: "TA Modeling")

- the general "flow"  of a test. What are the steps? How optional?  How atomic the TA?

- how much of the "test operation" should transpire in the TA, e.g. for requirements that are more predicative (e.g. doc structure) than behavioral.

- the semantics of post-conditions

 

TA thread #2: The outcome of a TA (will rename the thread: "TA Outcome")

- beyond pass/fail : undetermined / inconclusive / error / warning ? What outcome belongs to the "test case"  vs. to the TA?

- wording the TA prose to make the outcome conditions explicit (even in presence of RFC2119 keywords)

- distinguishing the TA outcome (fail / pass...)  from its conformance interpretation (the IUT is conforming or not)

 

TA thread #3: Cross-TA flow and TA interdependencies (will rename the thread: "TA-to-TA Flow")

- pre-requisites

- chaining/combiningTAs

 

 

Is there anything that does not fall into these?

 

-Jacques