TPT User's Guide - PikeTec

Page 32 TPT User’s Guide
6.2.4 Add Unambiguous Variants
If there is just one path variant in an automaton, it can be selected on the scenario level or
scenario group level with the variant assignment being carried out on all subordinate scenarios
in the latter case. Select scenario or scenario group and use Insert | Add Unambiguous
Variants.
The function can be used even if a path variation occurs in the automaton. If a path has already been
selected in the respective scenario, the function will work as described above. If no path has been
selected, the function will stop the allocation of default values at the first path variation.
6.3 “Direct Definition” scenarios
As previously described in Modelling a Testlet by “Direct Definition”, definition equations are
determined at the scenario level, i.e. valid scenarios are already created with definition
equations during the modelling phase. Since the modelling of “direct definition” testlets
involves the definition of scenarios both have already been dealt with in section 5: Modelling a
Testlet by “Direct Definition”.
6.4 Parameter definition
There are three types of parameter available. Local parameters are only visible in TPT. Readonly
parameters are read from the test platform and cannot be changed in TPT. Exchange
parameters are either read from the test platform or modified within TPT and written to the
test platform before the test execution. Parameters can be altered for each scenario.
Figure 20: Parameter definition tab
Figure 21: Parameter read from the test platform
When parameters are used in the scenario hierarchy the value might be overwritten by a
scenario lower in the hierarchy. This enables the use of different parameter values for different
scenarios.