Download User Manual: MSC to C Test Code Generator

Validas MSC to C Test Code Generator, Version 0.9.6
2007/10/29
5.2.4 Errors
The detected errors are counted using the global variable iAllTestErrors
(declared in msc2c_debug module). This variable is statically initialized and
never reset, such that the user has to reset it, when restarting the tests
manually. In addition the errors occurred within one MSCs are counted
and reported at the end of every MSC.
Every reported error has a error kind (indicated by a number). The
available error kinds are described in the type Errors as declared in
msc2c_debug.h. The following error kinds are defined:
•
•
•
•
•
•
•
•
•
•
•
•
OverallTestTimeout,
ConditionViolated,
UnexpectedMessage,
MessageMissing,
WrongMessageSequenceEarly,
WrongMessageSequenceLate,
WrongMessageParameterValue,
WrongReturnParameterValue,
WrongLoopRepetitionNumber,
TimeAnnotationViolated,
NoTimeoutOfTimer,
WrongMSC2CConfiguration
When MSC protocols are generated the name of MSCs with errors are
prefixed with an “Error” tag. A typical example for an MSCs with errors
can be found in Figure 7. It shows the tagged name of the protocol MSC
(Error_At_11_21_21.970_MTest1) together with three errors. The kinds of
the messages can be found in brackts after the erron number, however
the textual description is equivalent to the error kind. Note that
unexpected messages are not displayed as messages, since they have no
model correspondence in the specification. Furthermore Figure 7 shows
that “two errors” seem to have the same number, however the second
error is just a description summarizing the two previous errors, and
therefore has no extra number
page 21