Comment: a means to associate a test assertion with the setting of a property (or with a value assigned to a variable)

[Stephen D Green <stephengreenubl@gmail.com>]

Comment on Test Assertion Model V1.0

 

Again, perhaps for a future minor version, I suggest there might be

an extension to the model to cater for the usage described in the

Test Assertion Guidelines V1.0 where a test assertion can be the

means to set a property or a property value (perhaps using the

variable entity to hold the property name). For example, a test

assertion might have extended semantics to allow that the outcome

of a test case based on it, rather than indicate some kind of failure

of conformance, etc., determine that a property be associated with

the test assertion if the test assertion's semantics evaluate to true.

One way might be to add an entity, called something like setVariable,

along with extended semantics to say that if the test case based on

the test assertion evaluates to true (or false in certain cases - see

previous comment) then rather than an outcome of pass, the outcome

will be that a certain value is assigned to the named variable. A weakness

with this approach is that the semantics depend on the existence or non-

existence of this entity (setVariable) in the test assertion so a stronger

mechanism might be preferred.

 

e.g.

 

class: setVariable {
 
  new-value : string (1)
  name : string (1)
  language : string (0..1)
 
}

Best regards

 

----

Stephen D Green