Download 36 TTCN Test Suite Generation

Using Autolink
Example 270: Syntax of test suite structure rules –––––––––––––––––––––––––––––
<TSStructureRule>
::= "PLACE" <AlternativeListOfTerms>
<TSStructureRuleIf>*
[ <TSStructureRuleNoIf> ]
"END"
<TSStructureRuleIf>
::= "IF" <Conditions> "THEN"
<TSStructureRuleNoIf> "END"
<TSStructureRuleNoIf>
::= "IN" <Term> { "/" <Term> }*
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Declaring ASP and PDU Types
The rules to declare ASP and PDU types are evaluated when a TTCN
test suite is saved on disk with the Save-Test-Suite command. Please
note that each of the rules can only be defined once in an Autolink configuration. However, this is no restriction as you can specify an arbitrary
number of signals and sorts in both rules.
Example 271: Syntax for declaring ASP and PDU types ––––––––––––––––––––––––
<ASPTypesRule>
<PDUTypesRule>
::= "ASP-TYPES" <SequentialListOfTerms> "END"
::= "PDU-TYPES" <SequentialListOfTerms> "END"
Stripping Signals
Rules for stripping signals are evaluated closely coupled with the rules
above for declaring ASP and PDU types. Autolink only strips a signal
if its only parameter is declared as ASP or PDU. Autolink only accepts
one stripping rule in a configuration.
Example 272: Syntax for stripping signals –––––––––––––––––––––––––––––––––––
<StripSignalsRule> ::= "STRIP-SIGNALS" <SequentialListOfTerms>
"END"
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Functions
Functions are identified uniquely by their names. If there are two functions with exactly the same name, the one defined first is always evaluated.
Functions are visible globally, that is, they can be called by any constraint or test suite structure rule and other functions. References to
July 2003
Telelogic Tau 4.5 User’s Manual
,um-st1
1437