ETSI's Bug Tracker - Ext Pack: Advanced Matching (ES 203 022)
TTCN-3 currently is not able to support this kind of testing, as it is only able to send correctly encoded messages. But supporting this kind of operation is needed, to ensure the high quality of the tested systems.
To support this behaviour 2 (a static and a dynamic) support for negativ testing would be needed.
Please note, that:
- this would only need to have an effect on the transfer syntax of the send messages, the abstract values does not need to be changed.
- As these incorrect messages are used to test the SUT, it is not needed for the codecs to support decoding them.
- Also as this is special way of coding data, while it should be handled similar to alrady existing encoding/variant attributes ... it would be better have a new attribute kind for it.
Support for static negativ testing:
The request here is to be able to tell the system, that during encoding the message needs to be altered in some user specified way.
This only needs to apply values and templates of record, set, record of, set of and union types.
Currently we have identified the following needs:
- inserting some data before a field in the encoded message.
- overwriting the encoded value of a field (also setting mandatory fields to omit)
- inserting some extra data after the encoded value of a field.
For example:
template CX_Frame t_CX_Frame:=
{
data_length:=0,
data_stream:='AAABBCCDDEEFF1122‘O
} with
{
erroneous (data_length) “after(raw) := 'FF'O “;
erroneous (data_length) “value(raw) := 'AABBCC'O “;
erroneous (data_length) “before(raw) := 'FF'O “;
}
Would like this encoded: ‘FFAABBCCFFAAABBCCDDEEFF112’O
/* the data_length fields encoded value is replaced by 'AABBCC' and also prefixed and postfixed with 'FF'O */
This static encoding has the benefits of being static (efficiently optimizable before execution) and for its attributes the mechanisms existing for encode/variant attributes can be used.
Support for dynamic negativ testing:
Extending the static support for negativ testing, it would also be needed to have a machanism for dynamically altering the erroneous attributes of values and templates.
for example having a value like:
"const MyRec c_myrec := { i:=1, b:=true }
with {
erroneous (i) “before := 123”
erroneous (b) “value := omit”
}
"
Inside the body of functions, altsteps, testcases these attributes could be updated like:
- @update(c_myrec) with { erroneous(i) “value := 3.5” } // the field i's value shall be overwritten, but nothing is inserted before field i and field b is also not omitted.
- @update(c_myrec); // no longer erroneous, all arreneous attributes are removed
| related to | 0007785 | closed | Jens Grabowski | Add Mutation annotations to the Value data type |
CR7763.docx (123,228) 17-07-2018 16:45http://oldforge.etsi.org/mantis/file_download.php?file_id=3767&type=bug
CR7763-2.docx (133,303) 20-07-2018 09:01http://oldforge.etsi.org/mantis/file_download.php?file_id=3783&type=bug