Re: [tag] Test Assertion Modeling - comments, etc

["Dave Pawson" <dave.pawson@gmail.com>]

On 13/08/07, Durand, Jacques R. <JDurand@us.fujitsu.com> wrote:


> Then there are issues like - how to model 'SHOULD', can there be artifacts
> of artifacts, properties of properties, and can this complexity even be
> modelled as a set of predicatives, etc?
>
> <jacques> one way to handle SHOULD or RECOMMENDED reqs, is to treat them
> like MUST in the TA, but in case of failure, produce a "warning"  instead of
> a "fail"...


The more general model is for each test (however derived) to have an outcome:
That outcome is pass or fail. The action on fail can then be a reported fail (
of the entire test suite) or a warning message only. That should be a
part of the
test definition.

regards



-- 
Dave Pawson
XSLT XSL-FO FAQ.
http://www.dpawson.co.uk