|jdur...@us.fujitsu.com||Sep 19, 2007 5:24 pm|
|Dave Pawson||Sep 19, 2007 11:57 pm|
|Dave Pawson||Sep 20, 2007 12:21 am|
|step...@systml.co.uk||Sep 20, 2007 6:47 am|
|Dave Pawson||Sep 20, 2007 6:53 am|
|step...@systml.co.uk||Sep 20, 2007 10:45 am|
|Durand, Jacques R.||Sep 20, 2007 2:36 pm|
|step...@systml.co.uk||Sep 20, 2007 11:29 pm|
|Dave Pawson||Sep 20, 2007 11:53 pm|
|Dave Pawson||Sep 21, 2007 12:01 am|
|Dave Pawson||Sep 21, 2007 12:05 am|
|step...@systml.co.uk||Sep 21, 2007 9:10 am|
|step...@systml.co.uk||Sep 21, 2007 1:15 pm|
|Dave Pawson||Sep 21, 2007 10:36 pm|
|step...@systml.co.uk||Sep 22, 2007 2:26 am|
|Dave Pawson||Sep 22, 2007 5:11 am|
|Subject:||Re: [tag] Groups - TA Anatomy V0.4 (AnatomyTA-v04.doc) uploaded|
|Date:||Sep 22, 2007 2:26:19 am|
I think we are saying the test result should be discarded as 'inapplicable', 'fail'(??), 'error' or 'inconclusive' if the post condition isn't true or pass.
We do have a legacy of uncertainty about post conditions (I find it unclear how a condition is post and not pre) but it is part of things we should align to, I guess.
Some just use it as an extension of 'result', others as a way to describe preconditions for a subsequent step in the flow (a precondition before considering the next step perhaps)
We kind of accept that a post condition is like a result but doesn't determine the result, it determines the final value of the TA as whole. I agree with your clarification that we should consider particularly this overall outcome result. It has to be distinguished from the flow result (and would be likely to have a set of values including pass and fail whereas the flow result is more likely to evaluate to true or false)
-- Stephen Green
Partner SystML, http://www.systml.co.uk Tel: +44 (0) 117 9541606
Quoting Dave Pawson <dave...@gmail.com>:
So there is no pass or fail of the TA I gather but isn't it written as if there is? That confuses me a bit (it needs careful wording which I haven't attempted to figure out).
The TA isn't the test case so it doesn't evaluate to anything. It just gives information to the test case about how it ought to be evaluated to fulfil spec requirements, say (or on the test based on the test case based on the TA).
Yet we have determined the beginning of rules to say something like that a postcondition or precondition which evaluates to false means the test should evaluate to 'not applicable'.
How can test execution be based on a post condition?
The post condition is established when the test has run, hence cannot be used by the test, since by definition it has not completed if it is evaluating a post condition?
-- Dave Pawson XSLT XSL-FO FAQ. http://www.dpawson.co.uk