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

http://www.biblegateway.com/passage/?search=matthew+22:37 .. and voice

Quoting Dave Pawson <dave...@gmail.com>: