TPT User's Guide - PikeTec

TPT User's Guide
Version 3.1
13 February 2009

Contents
Page 2 TPT User’s Guide
TPT User's Guide _________________________________________________________________ 1
1 Introduction ________________________________________________________________ 5
1.1 Starting TPT ________________________________________________________________ 5
1.1.1 General options _____________________________________________________________ 5
1.1.2 Specific options of the execution _______________________________________________ 6
1.1.3 Specific options of the assessment engine _______________________________________ 6
1.1.4 Specific options for the data converter __________________________________________ 6
1.1.5 Specific options for the log server ______________________________________________ 6
1.1.6 Specific options for the report editor ____________________________________________ 7
1.1.7 Specific options for the report generator _________________________________________ 7
1.1.8 Further options _____________________________________________________________ 7
1.2 The main window ____________________________________________________________ 7
1.2.1 The testlet browser __________________________________________________________ 8
1.2.2 The scenario browser ________________________________________________________ 8
1.2.3 The editor window __________________________________________________________ 8
1.2.4 The documentation window __________________________________________________ 8
1.2.5 Menu and tool bar ___________________________________________________________ 9
1.3 Creating saving and loading test models __________________________________________ 9
1.4 Exit TPT ____________________________________________________________________ 9
1.5 View options ________________________________________________________________ 9
2 Declaration of Channels, Parameters and Constants _____________________________ 10
2.1 Introduction ________________________________________________________________ 10
2.2 The declaration _____________________________________________________________ 10
2.3 Creating a declaration ________________________________________________________ 11
2.4 Changing a declaration _______________________________________________________ 12
2.5 Deleting a declaration ________________________________________________________ 12
2.6 Declaration of Parameters _____________________________________________________ 12
3 Signature of a Testlet _______________________________________________________ 13
3.1 Introduction ________________________________________________________________ 13
3.2 Assigning observation channels ________________________________________________ 13
3.3 Assigning stimulation channels ________________________________________________ 14
3.4 Assigning local channels ______________________________________________________ 14
4 Graphical Modelling of a Testlet ______________________________________________ 15
4.1 Introduction ________________________________________________________________ 15
4.2 Creating initial node elements _________________________________________________ 16
4.3 Creating final node elements __________________________________________________ 17
4.4 Creating state elements ______________________________________________________ 17
4.5 Renaming states or testlets, respectively _________________________________________ 18
4.6 Embedded testlets __________________________________________________________ 18
4.7 Creating transitions __________________________________________________________ 19
4.8 Establishing transition specifications ____________________________________________ 19
4.9 Naming or renaming transitions ________________________________________________ 20
4.10 Shaping transitions graphically ________________________________________________ 20
4.11 Reconnecting transitions _____________________________________________________ 21
4.12 Creating junctions ___________________________________________________________ 22
4.13 Parallel automatons _________________________________________________________ 22
4.14 Creating textual notes ________________________________________________________ 22
4.15 Selecting, cutting, copying, inserting and copying as an image _______________________ 23
4.16 Saving automaton fragments __________________________________________________ 24
4.17 Importing TPT automaton fragments ____________________________________________ 24
4.18 Exporting automatons or automaton fragments into an image file ____________________ 24
4.19 Controlling quality and size of the automaton view ________________________________ 25
4.20 Compiling on the fly _________________________________________________________ 25

TPT User's Guide Page 3
5 Modelling a Testlet by “Direct Definition” ______________________________________ 26
5.1 Introduction ________________________________________________________________ 26
5.2 Defining Equations __________________________________________________________ 27
5.3 Changing the order of definition equations _______________________________________ 27
5.4 Defining signals _____________________________________________________________ 28
6 Definition of Scenarios ______________________________________________________ 29
6.1 Introduction ________________________________________________________________ 29
6.2 “Time Partition” scenarios _____________________________________________________ 29
6.2.1 Selecting path variants ______________________________________________________ 30
6.2.2 Selecting state variants ______________________________________________________ 30
6.2.3 Selecting transition specifications _____________________________________________ 31
6.2.4 Add Unambiguous Variants __________________________________________________ 32
6.3 “Direct Definition” scenarios ___________________________________________________ 32
6.4 Parameter definition _________________________________________________________ 32
6.4.1 Exchange Parameter with MATLAB ____________________________________________ 33
7 Organisation of testlets _____________________________________________________ 35
7.1 Introduction and scenarios ____________________________________________________ 35
7.2 Creation of testlets __________________________________________________________ 35
7.3 Deletion of testlets __________________________________________________________ 35
7.4 Deletion of the content of a testlet ______________________________________________ 35
7.5 Renaming testlets ___________________________________________________________ 36
7.6 Creation of scenarios / scenario groups __________________________________________ 36
7.7 Deleting scenarios / scenario groups ____________________________________________ 37
7.8 (Re)naming scenarios/scenario groups __________________________________________ 37
7.9 Moving scenarios ___________________________________________________________ 37
7.10 Commenting scenarios/scenario groups _________________________________________ 38
8 Test set configurations ______________________________________________________ 39
8.1 Introduction ________________________________________________________________ 39
8.2 Selection of test-sets _________________________________________________________ 39
9 Platform configuration ______________________________________________________ 41
9.1 Introduction ________________________________________________________________ 41
9.2 Selecting the platform________________________________________________________ 41
9.3 MATLAB/Simulink environment ________________________________________________ 41
9.4 The executable platform ______________________________________________________ 49
9.4.1 TPT-VM-API for the execution platform _________________________________________ 50
9.4.2 Executable platform configuration _____________________________________________ 51
9.4.3 Test Source Code with the Exe-Platform ________________________________________ 51
9.5 Standalone platform _________________________________________________________ 54
10 Test Execution _____________________________________________________________ 55
10.1 Introduction ________________________________________________________________ 55
10.2 Test execution configuration __________________________________________________ 55
10.3 Pauses or “Intermission points” ________________________________________________ 57
11 Test Analysis _______________________________________________________________ 59
11.1 Introduction ________________________________________________________________ 59
11.2 The Test Data Viewer _________________________________________________________ 59
11.2.1 Test data viewer operational modes and shortcuts ________________________________ 61
11.3 The HTML Report ____________________________________________________________ 62
11.3.1 Report overview ___________________________________________________________ 63
12 The Report Template Editor __________________________________________________ 64
12.1 Introduction ________________________________________________________________ 64
12.2 Creating a template by means of the template editor _______________________________ 64
12.3 Loading and saving a template ________________________________________________ 66
12.4 Elements of a template _______________________________________________________ 66
13 Function Wizard ____________________________________________________________ 69

Page 4 TPT User’s Guide
13.1 Motivation and targets _______________________________________________________ 69
13.2 Access to the function wizard __________________________________________________ 69
13.3 The individual functions ______________________________________________________ 70
13.3.1 Constant function __________________________________________________________ 70
13.3.2 Ramp function _____________________________________________________________ 70
13.3.3 Asymptote function ________________________________________________________ 71
13.3.4 Periodic function ___________________________________________________________ 71
14 Debugging of Test Automatons_______________________________________________ 73
14.1 Basic modules of debugging __________________________________________________ 73
14.2 Debug plug-in features _______________________________________________________ 74
14.2.1 Extensions to the user interface: definition of breakpoints __________________________ 74
14.2.2 Finding breakpoints ________________________________________________________ 75
14.3 Executing a test for debugging ________________________________________________ 76
14.3.1 Configuring the execution of tests in debugging _________________________________ 76
14.3.2 Sequence and operation of an execution during debugging ________________________ 77
14.3.3 The “control debug session“ window ___________________________________________ 78
14.3.4 The “channel watch” window _________________________________________________ 79
14.3.5 The “breakpoints overview” window ___________________________________________ 79
15 Further TPT functions and tools ______________________________________________ 80
15.1 TPT help system _____________________________________________________________ 80
15.2 The search an replace function _________________________________________________ 80
15.3 The history function _________________________________________________________ 81
15.4 Auto-completion ____________________________________________________________ 81
15.5 Menu Options ______________________________________________________________ 82
15.6 Interface import _____________________________________________________________ 82
15.7 The logging server ___________________________________________________________ 83
15.8 Statistics ___________________________________________________________________ 83
15.8.1 First column – Object overview _______________________________________________ 84
15.8.2 Second column - Amount ____________________________________________________ 84
15.8.3 Third column – Spreading of variants ___________________________________________ 84
15.8.4 Fourth column – Spreading of combinations ____________________________________ 84
15.9 Restore from history _________________________________________________________ 84
15.10 Environment variables _______________________________________________________ 85
15.10.1 Definition of environment variables ____________________________________________ 85
15.10.2 Execution Configuration variables _____________________________________________ 85
15.10.3 General platform configuration variables _______________________________________ 86
15.10.4 MATLAB platform configuration variables _______________________________________ 86
15.10.5 Backbone platform configuration variables ______________________________________ 86
15.10.6 Scenario specific variables ___________________________________________________ 86
15.10.7 Overview _________________________________________________________________ 88
16 Index _____________________________________________________________________ 89

TPT User's Guide Page 5
1 Introduction
The TPT User Guide is an introduction to using TPT. Beginning with an explanation of the
contents of the main window, this document will introduce features of TPT step by step, to
enable a user to model, execute and document their own tests using TPT.
Please note this document is not intended to be a tutorial. Basic understanding of the tool’s
fundamental concepts and techniques is required.
1.1 Starting TPT
TPT is started by executing its program file named tpt.exe, which can be found at its
installation location. Either call tpt.exe directly from the Windows Explorer (or shortcut) or
start it from the windows command line or DOS shell.
When using the command line, parameters may be used with the following syntax:
tpt.exe [general options ...] [specific options…]
General options can always be used, whereas specific options are only permitted if TPT is
started in a particular mode by using the option –run (see below).
1.1.1 General options
-c configfile, --config configfile
TPT saves global settings in a configuration file. By default, this file is assumed to be located at
/TPT/tpt.config, where represents the user’s local application
data folder (e.g. C:\Documents and Settings\username\Local
Settings\Application Data). This option allows you to specify an alternative
configuration file, which may be useful if, for example, several users need to share common
configurations.
-h, --help
Displays a help text on the console that explains all command line options.

Page 6 TPT User’s Guide
--nosplash
Suppresses the splash screen that is displayed while TPT starts up.
--plugins plugin1,plugin2,…, pluginN
In order to be able to dynamically integrate with area or domain-specific tools and its features,
TPT comes with a flexible plug-in architecture. All plug-ins are installed to a TPT subdirectory
named \tptplugins. By default, all plug-ins are loaded automatically by TPT. Use this
option, if you want to specify directly, which plug-ins are to be loaded on startup. Multiple
plug-ins may be specified using a comma-separated list.
filename
If tpt.exe is started without using the option --run, a filename may optionally be stated
as the command line’s last parameter. If the filename exists and is recognized as a valid TPT
model or data file, it will be loaded after start-up.
1.1.2 Specific options of the execution
--run build TPT-file-name execution-configuration
Starts the build and execution process of the specified TPT-file-name and executes the
execution-configuration specified. For the execution configuration please refer to
section 10.2.
1.1.3 Specific options of the assessment engine
--run assessmentengine [(-v|--var) vardef] ... scriptfile1
scriptfile2 ...
Starts the assessment engine and executes the scripts scriptfile1, scriptfile2 etc. one
after the other. If one or more variables have been defined with the option -v or –var, these
definitions are also passed to the scripts.
For example, if the argument --var foo=bar has been stated, the variable foo is
automatically defined within the script and has the value bar.
--run assessmentengine –-convert tptfile1 tptfile2 ...
Translates all assessment scripts found within the given TPT model file from the old assessment
language, used in early versions of TPT, into the new Python-based assessment language, that
hasen introduced with version 2.0 of TPT.
1.1.4 Specific options for the data converter
--run dataconverter inputfile [(-I|--Inputtype) inputtype]
outputfile [(-O|--Outputtype) outputtype]
This option provides a command line interface that allows conversion of data files (test records,
measurements…) from one supported file format to another. The input file’s and output file’s
type may explicitly be determined with the two additional options Inputtype and Outputtype.
Allowed types are: tptbin, mat or csv. If the files’ types are not explicitly given, TPT tries to
interpret the type from the file’s extension (.tptbin, .mat or .csv).
Please note that unequally sampled data cannot be saved as .tptbin format. This means that unequally
read data read from e.g. .csv will result in empty data block in the .tptbin-format.
1.1.5 Specific options for the log server
--run logger
This starts the log server instead of the TPT GUI. In order to aid debugging of software defects
while working with TPT, the log server’s entries provide an insight into internal operations and
their result.

TPT User's Guide Page 7
1.1.6 Specific options for the report editor
--run reporteditor
Starts the report template editor from the command line. It allows creation and editing of
report templates.
1.1.7 Specific options for the report generator
--run report inputfile templatefile outputdirectory referencefile
Starts the TPT report generator from the command line. All signals of the given input will be
read in be used for the report generation. The template file defines the report’s desired layout
and content. Resulting documents and dependent files are written to the output directory once
report generation is complete. If you provide a reference file, that contains a set of signals from
a previous test execution or assessment, the generated report will automatically include a
signal comparison for all signals.
1.1.8 Further options
The following options are general options that are not commonly used by TPT users.
--startverbose
Using this option causes TPT to output additional trace information while it starts up. These
outputs include start parameters and paths. This option is especially helpful, when problems
are encountered during TPT’s start-up procedure .
-vm-xxxxx
This option may be used for specifying additional parameters which are specific to the Java
Virtual Machine. These parameters allow setting and fine-tuning a Java VM’s memory
consumption and different modes of operation. They always start with the prefix -vm and will
be propagated and applied to the underlying Java VM.
Example: -vm-Xmx250m sets the maximum heap size of the Java VM to 250MB.
--Xea
Enables internal assertion checking in order to detect assertion violations during TPT runtime.
This mode of operation is only required for the debugging of TPT.
1.2 The main window
After TPT has loaded, it displays a window containing a menu bar, a tool bar and an empty
workspace. Opening a TPT model file will show its contents within a multiple-segmented frame
of the workspace. The following section gives a brief introduction to these elements.

Page 8 TPT User’s Guide
Testlet browser
Scenario browser
Documentation
window
1.2.1 The testlet browser
Editor window
Figure 1: TPT's program window
The area in the upper left corner of the main window (see Figure 1) is called the testlet browser.
It depicts the test model’s testlet hierarchy as a tree structure and provides a set of operations
on testlets, which are described in Organisation of testlets.
1.2.2 The scenario browser
The scenario browser displays the hierarchical representation of all scenarios a testlet owns,
(see Figure 1) and the scenario tree of the currently selected testlet. Furthermore, the scenario
browser provides several options for modifying the scenario hierarchy, such as creating new
scenarios and deleting existing ones. The scenario browser allows a user to build a complex
hierarchy of a large number of scenarios. Please see section 7 (Organisation of testlets) for a
more detailed description of the scenario browser.
1.2.3 The editor window
While the browsers for testlets and scenarios provide access to the structure of testlets and
scenarios, the editor area on the right (see Figure 1) is used to access and edit different aspects
of smaller elements. It thus has several editor tabs like “content”, “signature“ and “assessment”.
Details on how to define a test case’s signature and create test assessments can be found in
sections 3, 4, 5 and Definition of Scenarios .
1.2.4 The documentation window
A simple text area below the scenario browser (see Figure 1) enables a user to create and edit a
short description text, which is stored with the currently selected scenario. Read more on how
to document scenarios and scenario groups in section 7.10 (Commenting scenarios/scenario
groups).

TPT User's Guide Page 9
1.2.5 Menu and tool bar
TPT comes with a menu and tool bar (see Figure 1), allowing a fast and intuitive access to
frequently used options and features. The following section introduces some of these options.
1.3 Creating saving and loading test models
1.4 Exit TPT
To create a new test model, one may choose File | New from the menu bar or type
Ctrl+N). After modelling some tests, one may want to save the work by choosing the menu
item File | Save or by using the corresponding hotkey Ctrl+S. When a test model is
saved for the first time or menu item File | Save as... is used, a location and a
filename will be requested.
Load a project by using the menu item File | Open or by typing this option’s associated
shortcut key (Ctrl+O).As for other commonly used menu options, you can find corresponding
items on the tool bar, that are additional controls for activating the same features
Each TPT test model is saved to a single XML TPT model file, and usually suffixed with “.tpt”.
One can exit TPT by clicking the x-shaped “Close” symbol of its application window, by
selecting the menu item File | Exit, or by using the shortcut key Ctrl+Q. If the loaded
test model has been changed since the last save operation, a confirmation dialogue will ask the
user whether to save these changes or discard them.
1.5 View options
To zoom the TPT-model, browse forward and backwards, use a layout mesh grid or change the
tool-bar icon size one may choose View | ... .

Page 10 TPT User’s Guide
2 Declaration of Channels, Parameters and
Constants
2.1 Introduction
Each test model has an interface, which is defined by a set of observation and stimulation
channels (in the case of single testlets, this is also referred to as the “signature” of the testlet).
Besides interface channels, TPT provides for additional channel types, constants and
parameters for supporting different test functions, like measuring signals and assessing test
results.
All channels, constants and parameters must be declared before they can be used in a test
model. This is done in the declaration editor.
2.2 The declaration
The declaration editor (see Figure 2) can be opened via the menu bar by selecting View |
Declarations or by the associated hotkey, which is Ctrl+D. A table is displayed which
may contain different channel types, constants and parameters. Each column describes
attributes associated with a declaration, like a name, a data type and a description.
The entries can be sorted by any of the column categories. The default is the name column, but
any other may be selected by clicking on the heading in the table header row.
There is also a collapsible panel above the table which allows a user to filter declarations based
their type (channel, constant …), name or description.
Entries may be edited by clicking on them. New declarations are appended in the area below
the table.
The declaration editor can be closed using the “Close” button or by using the close icon at the
top-right of the window.

TPT User's Guide Page 11
2.3 Creating a declaration
Figure 2: The declaration editor
In order to create a new table entry one has to empty the editor’s input fields located right
below the table by clicking the button labelled “Clear” and then fill these fields with the values,
that describe the new entry:
Type
This drop-down list allows a user to choose which type of declaration is to be created.
Name
This text input field expects a unique string for the new declaration which must follow the
restrictions imposed by TPT.
Location
This text field takes an optional URI that may contain additional information about a
declaration’s external location (if it has one). The exact semantics of an “external location” are
specific to different test execution environments.
Group
This text field takes an optional arbitrary group name, which may be used to easily categorize
declarations according to the user’s requirements.
Data Type
This drop-down list requires a data type to be chosen for the new declaration.
Value
This text field expects a default value to be entered for the declaration. Naturally this value has
to be compatible with the selected data type.
Volatile
This check box is only available for channels. When selected, the channel to be created will be
“volatile”, which refers to the behaviour of the values of the channel over time. While a value
that has been written to a non-volatile channel at a certain point in time persists to later times,
a volatile channel discards its current value when time increments to the next ‘instant’.

Page 12 TPT User’s Guide
Record
This check box is applicable to channels, measurements and assessment variables. When
selected, the values of the object declared will be recorded and stored during a test execution.
Description
This allows an arbitrary text description field to be applied to the object.
Once all mandatory settings and attribute values have been entered correctly, the “Apply”
button will be enabled which adds the newly created declaration to the table.
2.4 Changing a declaration
Any attribute of a declaration may be changed except its type. In other words, a channel cannot
be converted to be a constant and vice versa. The editor panel below the table may be used to
change the attribute values of the declaration selected in the table. The changes will be applied
after being confirmed by the “Apply” button.
2.5 Deleting a declaration
Declarations may be deleted by selecting them in the overview table and then using the
“Delete” button.
2.6 Declaration of Parameters
Parameters can be used within the tests. Parameters are similar to constants but can be
modified for each test run. Parameters can be of different types. Local parameters are only
visible within TPT. Read-only parameters are read from the simulation environment but cannot
be changed. Exchange parameters are exchanged between TPT and the simulation
environment. Please note that further settings at the execution platform may be necessary.
Figure 3: Parameter declaration

TPT User's Guide Page 13
3 Signature of a Testlet
3.1 Introduction
Each testlet has a signature which consists of stimulation, observation and local channels.
Channels may be assigned using the “signature” tab from the main window. The currently
selected testlet is represented by a grey rectangle and channels are displayed as arrow-headed
lines. Stimulation channels are shown on the right of the testlet and observation channels on
the left, local channels are shown within the testlet rectangle (see Figure 4).
The following sections describe how to create or alter the signature of a testlet.
3.2 Assigning observation channels
Figure 4: The testlet signature
A new observation channel may be added to a testlet’s signature by moving the mouse over
the area to the left of the testlet and clicking the left mouse button. A pop-up window appears
which contains two list boxes, one on the left and one on the right side of the dialog box. The
list on the left side shows all channels that are known to the system, but are not yet assigned to
the current testlet’s signature (see Figure 5). If there are no channels that might be assigned to
the testlet, this list will be empty.
If channels are available they can be added to, or removed from the set of observation channels
on the right hand side.

Page 14 TPT User’s Guide
Channels will appear in the signature window when either the “Apply” or “OK” button is used.
If an observation channel that is to be assigned has already been set as a stimulation channel or local
channel, a pop-up window will open up, pointing out this conflict. The channel can be reassigned to its
new role or left as it is.
3.3 Assigning stimulation channels
Figure 5: Assigning observation channels
Assigning stimulation channels is done similarly to the assignment of observation channels
(see section 13 Assigning observation channels), other than the pop-up menu opens when
clicking on the right hand area of the signature box.
3.4 Assigning local channels
The assignment of local channel uses the same method. The pop-up window will be opened
when clicking within the signature box.

TPT User's Guide Page 15
4 Graphical Modelling of a Testlet
4.1 Introduction
The following sections describe the features used to build a test model, i.e. how to construct
and edit a time partition automaton using the graphical elements. These elements are “initial
nodes”, “final nodes”, “states”, “transitions”, “junctions” and ”parallelisation separators”.
To start modelling a testlet, select it in the testlet browser. The “content” tab of the main
window will then show three option buttons to select either the “time partitioning” ,
“reference” or the “direct definition” method. Select “time partitioning” (see Figure 6). Now you
can start to construct the process automaton that belongs to the testlet.
Testlets in the testlet browser, that have not yet been modelled, are marked with a grey question mark
which is placed next to the testlet name. Testlets which have been modelled using the “time partition”
method are shown with a grey symbol that resembles an arrow, while three parallel horizontal lines
indicate a testlet that has been used by the “direct definition” method.
Note: Automatons may only be modelled or changed if no scenario is selected in the scenario browser, i.e.
only if the current testlet located in the scenario browser root node is marked there! The reason for this is
that one and the same TPT automaton is the basis for all assigned scenarios.

Page 16 TPT User’s Guide
4.2 Creating initial node elements
Figure 6: Selecting the modelling variant
To create an initial node select Insert | Junction in the menu, use the corresponding
symbol in the toolbar or the appropriate hotkey F5. Left-click into the “content” tab work area
where you want to create the new initial node. It will be represented by a filled black circle (see
Figure 7).

TPT User's Guide Page 17
initial node
junction
Figure 7: Elements of the graphical testlet model
final node
TPT junctions and initial nodes differ in that initial nodes are not linked to incoming transitions. Thus,
there is no specific symbol or menu entry for initial node elements.
4.3 Creating final node elements
To create a final node select Insert | Final from the menu or use the assigned hotkey
F3. Place the final node in the “content” tab by left-clicking at the desired position. A final node
is represented by the silhouette of a black circle (see Figure 7).
4.4 Creating state elements
To create a state select Insert | State or use the assigned hotkey F2. Left-click in the
“content” tab work area where the state symbol is to be placed. A state is represented by a
yellow or green filled rectangle, depending on whether it contains only simple definitions
(yellow) or another automaton (green). The name of the testlet that is assigned to the state
appears within the rectangle (see Figure 8).
The creation of a state corresponds to the creation of a new testlet. Therefore every state also appears as a
testlet in the testlet browser. This new testlet or state also has to be modelled, either as a sub-automaton
with “time partitioning” or per “direct definition” by means of state equations.

Page 18 TPT User’s Guide
New state elements
appear as testlet in testletbrowser
State elements
Figure 8: State elements
4.5 Renaming states or testlets, respectively
State elements
A new state or testlet receives an automatically generated name during its creation (“testletxx”).
Change the name by first selecting the testlet within the automaton or the testlet browser,
then use F2 or left-click on the state symbol. After a slight delay a cursor appears within the
symbol and the new name can by typed.
To enter names that consist of multiple lines press ENTER to move the cursor to the next line,
and SHIFT+ENTER to finish editing.
4.6 Embedded testlets
As mentioned previously a testlet is assigned to each state (which has been modelled with
“time partition” or “direct definition”). The hierarchy of testlets is reflected in the testlet
browser. To directly select a testlet shown within any of the tabbed work areas, click on the
corresponding testlet’s entry in the testlet browser. You will immediately see the content of the
selected testlet in the “content” tab of the main window, either in the form of an associated
sub-automaton or as a set of equations.
Alternatively, you may select the content of a testlet by double-clicking on the state assigned to
it in the currently displayed automaton. If this testlet in turn is an automaton, this can be
repeated until you encounter a testlet that has been modelled with definition equations. Such
a testlet may not contain other testlets.
The overall test model is finished only if all testlets are have been modelled completely and correctly. If
the testlet browser still contains testlet nodes with grey question marks, the modelling of these testlets
has not been completed.

TPT User's Guide Page 19
4.7 Creating transitions
To create a transition select the Insert | Transition or use the assigned hotkey F4.
Then, in the “content” tab work area click once on the initial node, junction or state, from which
the transition should start. Click again on the final node, junction or state at which the
transition should end.
Transitions themselves may neither be copied nor cut individually, since they are linked to source and
target objects. See Selecting, cutting, copying, inserting and copying as an image for further editing
options.
If a transition is created, it is displayed as a straight arrow. However, it is also possible to give the transition
the form of a Bezier curve (see Shaping transitions graphically).
4.8 Establishing transition specifications
Every transition has one or more “transition specifications” assigned to it. Each transition
specification consists of a formal condition and action statements (see Figure 9). To define one
or more transition specifications, double-click on a transition in the automaton. The transition
editor opens, which shows the list of available transition specifications on the left side
(“transition tree”) and formal conditions and actions on the right.
To create a new transition specification, carry out the following steps, preferably in the given
order:
Creating a transition specification
A new and empty transition specification is created by clicking the “Add New” button (see
Figure 9).
Entering a formal condition (optional)
On the right-hand side of the transition editor, enter the desired transition condition into the
text field (“formal condition”) (see Figure 9).
Entering action statements (optional)
On the right-hand side of the transition editor, enter the desired actions into the text field
“actions” (see Figure 9).
Transition specifications may be deleted by selecting the corresponding transition specifications in the
transition editor and then using the “delete” button.

Page 20 TPT User’s Guide
Four different transition
specifications
Named transition
4.9 Naming or renaming transitions
Transition editor
Figure 9: Establishing a transition specification
Transitions that have just been created will initially have no label. Once a transition has been
given a label, it will also appear in the automaton. To set a new or change an existing label text,
left-click on the desired transition and edit the text in turquoise label box.
A transition’s label may be placed arbitrarily and independently of the transition’s position within the
displayed automaton by using “drag & drop” (keep the left mouse button pressed on the transition label
and move the mouse). In case, you are unclear about which transition owns which transition label, just
select the symbol or the name in question. Both the transition symbol and its label will be highlighted.
4.10 Shaping transitions graphically
Transition symbols are not restricted to straight lines. Considering rather complex models it
makes that transitions may also form curves to retain clarity in the graphical representation.
Therefore TPT allows transition symbols to form Bezier curves.
Adding a control point to a transition
To add a new Bézier control point to a transition left-click and hold on the symbol. When the
pointer is dragged away from the transition, a red Bézier control point appears beneath the
pointer and follows it. The curve is updated as you change the control point’s position, until the
mouse button is released.
Further control points can be added, enabling a user to create almost any desired curve (see
Figure 10).

TPT User's Guide Page 21
Figure 10: Forming transitions graphically
Moving control points of a transition
To change the path of a selected curved transition click and drag the control point to its new
position.
Removing control points from a transition
To remove one of its control points, select the transition with the left mouse button, click on
the control point that is to be removed and then delete using Edit | Delete or the DEL
key.
The two control points at the beginning and the end of the transition arrow may not be moved or
deleted.
4.11 Reconnecting transitions
Transitions have to be connected to both a source and a target object to be valid. It is not
possible to “disconnect” an individual transition and to reinsert it at another point.
However, the source object and the target object that belongs to a transition may still be
exchanged once a transition has been created.
Changing the source object of a transition
Select the transition that should be reconnected. The transition and all its control points will
then be displayed in blue. Now select the control point (which thereby turns red), that is next to
the object from where the transition starts (an initial node, junction or state). Drag the mouse
pointer to the new source object. Release the mouse button to complete connection to the
new source object.
Changing the target object of a transition
This is the same as for changing source object: click and drag the arrowhead to the new target
object, then release.

Page 22 TPT User’s Guide
Reconnecting the end points of a transition requires exact mouse positioning. If the original source or
target object is suddenly selected or if a new Bezier control point is suddenly created, you most likely have
missed the exact position of the transition’s start or end point.
4.12 Creating junctions
To create a junction use Insert | Junction or the assigned hotkey F5. Left-click at the
desired position within the automaton in order to create it. A junction is represented by a solid
black circle.
All editing options described in Selecting, cutting, copying, inserting and copying as an image are
applicable to junctions. Note, that deleting a junction will delete all its incoming and outgoing transitions.
4.13 Parallel automatons
A testlet may consist of any number of parallel automatons. In the automaton view these are
displayed as work areas separated by horizontal lines.
To create a dividing line use Insert | Junction or the assigned hotkey F1. Go to the
“content” tab and left-click where the line is to be positioned (see Figure 11).
Ensure that no automaton element crosses a horizontal separator line.
You may later move the dividing line up or down by selecting and dragging it.
4.14 Creating textual notes
Figure 11: Parallel automatons
Textual notes are used solely for documenting an automaton or its elements.
Separation line
Separation line

TPT User's Guide Page 23
To create a text node use Insert | Text or the hotkey F7. Then left-click at the position at
which you want to create the new note. It is edited by clicking inside the text box or using F2.
All editing features described in Selecting, cutting, copying, inserting and copying as an image are also
applicable to text nodes.
4.15 Selecting, cutting, copying, inserting and copying as an image
Selecting individual automaton elements
Individual elements of an automaton (initial and final nodes, junctions, states, text nodes and
transitions) may be selected by clicking on the element using the left mouse button. Its colour
will change to blue as the element is selected.
Selecting multiple automaton elements
Multiple elements can be selected by clicking and dragging diagonally in the work area to
select elements within the rectangle.
Alternatively holding the Ctrl key will allow cumulative selection of elements by left-clicking
on them.
A transition will automatically be included in a selection, if both of its connected elements have been
selected.
In order to select all elements of an automaton (in other words: the entire automaton), one may use
Edit | Select All from the menu or by using the corresponding hotkey Ctrl+A.
Clearing a selection
In order to clear a selection simply left-click on an empty area of the automaton.
Moving automaton elements
The position of a selected automaton element may be changed by dragging it with the mouse.
This also works on a compound selection of multiple automaton elements, in which case all
selected elements will be moved together.
A transition may not be moved independently as its position is linked to the positions of the elements, it
connects.
Deleting automaton elements
Select a single or several automaton elements and use the corresponding menu item (Edit |
Delete) or its assigned hotkey Del.
When deleting automaton elements, all their incoming and outgoing transitions, will be deleted, too,
since a transition must always be connected to both a source and a target element.
When deleting a state or a testlet all its embedded elements will be deleted as well (see Embedded
testlets).
Cutting out selected automaton elements
Select a single or multiple automaton elements and choose Edit | Delete or hotkey Ctrl+X. All selected
elements will be copied to the system clipboard and deleted from the automaton. They may be pasted
into other automatons of the same or even a different file.
A transition may not be cut out independently of the elements it connects. Both the elements have to be
cut out at the same time, in order to cut the transition out, too. Otherwise, the transition will not be
transferred to the system clipboard, but deleted.

Page 24 TPT User’s Guide
Copying automaton elements
Select a single or multiple elements from an automaton and use the menu item Edit | Copy or its
corresponding hotkey Ctrl+C. The selected elements are copied to the system clipboard and may
subsequently be pasted into other automatons of the same file or a different file.
Transitions may only be copied along with their source and target element.
Inserting automaton elements from the clipboard
Elements of an automaton, that have been transferred to the clipboard as a result of prior copy
or cut operations, may be pasted as normal using Edit | Paste or hotkey Ctrl+V. All
pasted elements will be selected after insertion, so that they may be moved to a desired
position within the automaton.
Automaton elements, that have been stored to the system clipboard, will reside there,
unaffected of subsequent paste operations, until they are overwritten due to a copy or cut operation. As
TPT makes use of the operating system’s clipboard, data copied or cut out in other applications may
replace the contents transferred to it by TPT just as well.
Copying automaton elements as an image to the clipboard
Select the automaton elements which you want to copy as an image to the clipboard and
choose Edit | Copy Image. The resulting image will be stored to the system clipboard
and may be imported to any image processing application, using the common “insert from
clipboard” feature (usually called “paste” and accessible using Ctrl+V).
In case, the “copy image” feature is triggered on an empty selection, which means, that no automaton
elements have been selected, TPT will create an image of the entire automaton that is currently displayed.
TPT offers various options which influence the look of the image. Please refer to Exporting automatons or
automaton fragments into an image file , in order to see which options are available and how they are
used.
4.16 Saving automaton fragments
TPT provides the possibility of saving automaton fragments to a new TPT file, allowing them to
be reused in any other test model.
Select all the automaton elements which you want to be exported and use File | Save
Selection As. You will be prompted to choose a location and a name for the new file.
When saving automaton elements, all information directly linked to them, such as scenarios, signatures,
channels and constants, sub-automatons and assessment statements will be saved as well.
4.17 Importing TPT automaton fragments
It has already been explained how automaton elements can be pasted from the clipboard.
Importing elements or fragments of an automaton from a file is just as easy. Select the menu
item Insert | File Content and chose the TPT file to be imported. The file’s contents
will be imported to the currently selected automaton.
4.18 Exporting automatons or automaton fragments into an image file
If you want to generate an image of an automaton or automaton fragment, select the elements
you wish to export as an image and choose File | Save Image As from the main menu.
If the “content” tab contains no selected elements an image will be created showing the
automaton as a whole.

TPT User's Guide Page 25
You will be prompted to choose a location and a name for the image file to save. It will be
encoded using the PNG image file format.
You may determine the resolution of the created image using the menu item “Image
Resolution” from the “Options” menu (Options | Image Resolution).
4.19 Controlling quality and size of the automaton view
The “content” tab either shows the automaton currently being edited or a scenario which has
been selected in the scenario browser. Because both can be quite large, TPT provides a vertical
and a horizontal scrollbar and allows changing the zoom factor of the display area, in order to
increase or reduce the size needed by a single automaton element.
Another feature, that allows controlling the visual appearance of automatons, is the “anti
aliasing”. If this feature has been enabled using the menu item Options | Smooth Lines
and Text, all elements of an automaton including labels will be “smoothed” for display.
Furthermore, you may enable the “auto-scroll” feature (Options | Scroll
Automatically), which will cause the display area to scroll automatically if you move
automaton elements to the edge of the displayed area.
4.20 Compiling on the fly
During test modelling the model is compiled and shows errors if the model has compilation
errors. The errors of model objects are marked in red as shown in
Figure 12. The tooltip shows the respective error message when moving the mouse to the error
marker.
Figure 12: Compilation error
The process of compilation usually updates automatically. Nevertheless the compilation can be
initiated actively (cf. Figure 13)
Figure 13: Refresh compilation

Page 26 TPT User’s Guide
5 Modelling a Testlet by “Direct Definition”
5.1 Introduction
While the previous section (see Graphical Modelling of a Testlet) dealt with modelling testlets
by means of process automatons, the following sections will introduce the second method
called “direct definition”.
To start modelling a testlet, select it in the testlet browser. The “content” tab of the main
window will then show three option buttons to select either the “time partition”, “reference” or
the “direct definition” method. Select “direct definition”. The work area will be replaced by a
new panel, which allows creation of a “direct definition testlet” (see Figure 14).
Every testlet that is specified using the “direct definition” method consists of an ordered list of
equations or a signal definition: one for every stimulation or local channel. These equations are
listed in a table view, which shows the target channel of each equation in the left column and
the associated expression in the right-hand column.
When a testlet model is created for the first time using “direct definition”, the table view will be
filled using the add button. Only the right-most column, containing each equation’s expression
will be left empty and needs to be completed.
A preview for the generated definition can be seen in the lower part of the window. More than
one signal can be displayed at the time by selecting more than one channels.
The definition of each equation’s expression has to be repeated for every scenario of the testlet.
This procedure will be explained in detail in the next section.
Testlets modelled by means of the “direct definition” method may not contain any further testlets and can
therefore always be found at the terminal end of any branch contained in the testlet hierarchy.

TPT User's Guide Page 27
5.2 Defining Equations
add channel
Definition equation
Signal editor window
Figure 14: Modelling by means of "direct definitions"
Before the equations of a testlet of type “direct definition” can be entered, at least one scenario
must be associated with the testlet. If no scenario is defined for the testlet, please create one
(see Definition of Scenarios). Additionally, the signature of the testlet should contain at least
one stimulation channel or local channel (see section 133: Signature of a Testlet).
To enter the equations of a scenario, select the scenario in the scenario browser. The “content”
tab will then display the table of equations for that scenario (see section 5: Modelling a Testlet
by “Direct Definition”).
Signals, which you want to assign to a channel, can also be modelled with the signal editor (see Defining
signals).
A function wizard exists to aid the channel definitions (cf. section 13).
When entering an expression, Ctrl+Space opens a popup that lists all channels that are available to
the expression. Using the Enter key on a channel will import it into the expression at the current cursor
position.
5.3 Changing the order of definition equations
The equations are evaluated in from top to bottom, thus the order is relevant. They may be
moved by drag and drop the channel to the new position. (see Figure 14).
In former versions of TPT it was possible to change the order of definition equations within the testlet for
every scenario individually. This is not possible anymore in the release 3.1 and may change the semantics
of former versions of TPT-files. These direct definitions must be checked manually in order to avoid
unexpected behavior when executing earlier versions of TPT-files with TPT 3.1 and higher.

Page 28 TPT User’s Guide
5.4 Defining signals
Signals can be defined graphically by using the signal editor (see Figure 15). Signal sample
points are created by double clicking in the signal editor window after selection of “Create
Signal”. The Points may be modified graphically by drag and drop or by using the sample point
table that can be found in the editor tool-bar.
Signal specifications may also be imported from external data. The import file format must
have a certain format. This is .tptbin, MATLAB .mat, csv, mdf (dat), as well as the TPT-formats
trec and tptbin. The Provetec TA file-formats (.hdr, .bin) is supported as well.
Please note that unequally sampled data cannot be saved as .tptbin format. This means that unequally
read data read from e.g. .csv will result in empty data block when saved as the .tptbin-format.
MATLAB .mat-file
The .mat file must contain the signal-vector(s) as well as a scalar variable named “StepSize”,
which represents the sample time [s]. Please note that the signal must be uniformly sampled
and the option “-v6” in MATLAB may be used.
CSV
The CSV file must contain a time column and at least one signal column. The first row of the file
denotes the files’ header, containing a “time” label in the first column and the name of each
signal in the subsequent columns. Each column must be separated by a semicolon, a comma or
whitespaces (including tab stop; see example).
time light_intentsity oscillation
0.002000 0.0 0.0
0.003000 0.2 0.0
Figure 15: Signal editor

TPT User's Guide Page 29
6 Definition of Scenarios
6.1 Introduction
Each testlet consists of a number of scenarios. For “direct definition” testlets each scenario is
just defined by an instance of the definition equations (definition variant). The next 3 sections
will describe how a valid scenario should be defined for “time partition” testlets. The following
assumes that you have already used the testlet browser to select the “time partition” type of
the testlet for which you want to model different scenarios.
6.2 “Time Partition” scenarios
Since an automaton represents each testlet of the “time partition” type, a scenario within a
testlet is only valid if an instance of the automaton is allocated to each scenario (see Figure 16).
This means one model variant of the automaton has been selected. The model of the
automaton is realised if the following conditions have been fulfilled:
• If there are multiple possible paths in the automatons, one specific path must be
selected
• A specific state must be selected for all possible states in the automaton. Since all
states are in turn testlets, this is equivalent to the selection of a specific scenario which
is allocated to the testlet (state variation).
• A transition specification from the set of transition specifications (which have been
defined in the transition editor) must be selected for all transitions in the automatons.

Page 30 TPT User’s Guide
6.2.1 Selecting path variants
Figure 16: Scenarios of a testlet
Use the scenario browser to select the scenario you want to model. If no scenario exists, create
one and select it. If there is a path variation in your automaton the whole automaton will be
greyed-out until a specific path has been selected. Left-click on the transitions on the path you
want for the current scenario. All automaton elements on this path will now be displayed in
their original colours again (see Figure 17).
You will find that it is not possible to select two alternating paths in the same scenario. If you
choose one alternative, the other will automatically be greyed-out.
Once a path for the current scenario has been defined in the automaton, the next step is to
select the state variants as described in the following section.
If there are no path variations in the automaton, the only possible path will already be selected
automatically.
You can use another left-click to remove a transition from the path at any time.
6.2.2 Selecting state variants
Figure 17: Selection of a path variant
Once a specific path variant has been selected red question marks will appear under each state
name. This means that no state variants have yet been allocated to these states. Right-click on

TPT User's Guide Page 31
each state and choose a specific state variant. The red question marks will now be replaced by
the names of the chosen variants (see Figure 18).
The pop-up menu always contains the menu item “undefine”. Selecting this item cancels an already
existing state variant allocation.
A state variant corresponds exactly to a scenario from the number of scenarios allocated to the testlet
“behind” the state.
6.2.3 Selecting transition specifications
Figure 18: Selection of a state variant
The selection of transition specifications is done at the same time as the selection of the state
variants. Once a selection has been made two red question marks will appear under each
transition name (if transitions are unnamed the question marks are located near the transition).
Right-click on each transition arrow or transition name and choose a transition specification in
the pop-up menu. The red question marks will now be replaced by the names of the chosen
specification (see Figure 19).
The pop-up menu always contains the menu item “undefine”. Selecting this item cancels an already
existing allocation of a transition specification.
Figure 19: Selection of a transition specification

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.

TPT User's Guide Page 33
The rules for defining parameters are as follows:
Local
parameter
defined in
TPT
scenarios
defined by
platform
meaning
yes (ignored) Local parameters are allowed if the parameter is defined
for each scenario. A potential definition in the platform is
not treated by TPT.
no (ignored) Local parameters are allowed even if the parameter is not
defined! In this case the default value (defined in
declaration editor) is used. A potential definition in the
platform is not treated by TPT.
Read-Only (ignored) yes Read-only parameter will be read from platform. The
default value is never used in this case.
(ignored) no Error. The parameter must be defined in the platform to
ensure consistency.
Exchange yes yes The definition provided by TPT is used, i.e. the platform
definition will be overwritten.
yes no The definition provided by TPT is used and transmitted to
the platform.
no yes The definition provided by the platform is used and
transmitted to TPT.
no no The default value (defined in declaration editor) is used
and transmitted to the platform.
As a rule, the priority of parameter values is TPT > Platform > Default Values (from declaration
editor). The objective is in general to have the same values for parameters for platform and test
case. If this is not possible, an error is raised.
Parameter can be defined as scalar parameter or as array parameter. Array parametersare
defined as follows:
Assume a parameter x having the values [1 3 5 7 9] this parameter is to be declared in the
declaration editor similarly and can be accessed in direct definitions and transition definitions
via x[index]. E.g. the value of x[1] is equal 3.
6.4.1 Exchange Parameter with MATLAB
The parameter exchange with the MATLAB platform is as follows. Generally the parameters are
read from the MATLAB-Platform when a MATLAB-variable having the same name exists. To
write parameters to MATLAB, the variable “tpt.matlab.paramstoworkspace” (see
section 15.10.4: MATLAB platform configuration variables) is used and must be added to the
test-run-script in the platform configuration (see Figure 22).

Page 34 TPT User’s Guide
Figure 22: MATLAB - TPT parameter exchange

TPT User's Guide Page 35
7 Organisation of testlets
7.1 Introduction and scenarios
The natural organization of testlets and scenarios is hierarchical, depicted as a tree in the testlet
or scenario browser. The possible organisational structures offered by the testlet and scenario
browsers are discussed in the following chapter.
7.2 Creation of testlets
New testlets cannot be created in the testlet browser. Since a testlet represents a state in the
automaton, new testlets appear in the testlet browser when a new state is created (see section
4.4: Creating state elements).
7.3 Deletion of testlets
Testlets can be deleted directly from the testlet browser. Right- click on the name of the testlet
and choose “Delete testlet” in the pop-up menu.
Deleting a testlet in the testlet browser is the same as deleting the state element represented by this
testlet. If a testlet is deleted in the testlet browser, the associated state element is also removed from the
corresponding automaton and vice versa.
Deleting a testlet (or state) implies the deletion of all embedded testlets (see section 4.6: Embedded
testlets).
7.4 Deletion of the content of a testlet
It is also possible to delete just the content of a testlet, instead of deleting the testlet
completely. Right-click on the name of the testlet and choose “Delete content” in the pop-up
menu.

Page 36 TPT User’s Guide
All embedded testlets in the testlet (see section 4.6: Embedded testlets) are deleted, but the
signature and assessment statements are retained.
Deleting the content of a testlet (or state) implies the deletion of all embedded testlets.
7.5 Renaming testlets
In addition to being able to rename testlets or states from the automaton view (see section 4.5:
Renaming states or testlets, respectively), they may also be renamed from the testlet browser
by selecting then left-clicking again, after a slight pause, to enter the edit mode.
7.6 Creation of scenarios / scenario groups
A complex hierarchy of scenarios or scenario groups may be assigned to each testlet in the
scenario browser. Similar to folders in a file system, scenario groups serve the purpose of
grouping scenarios.
To create a scenario hierarchy select a testlet in the testlet browser. The name of the selected
testlet should appear in the scenario browser and the default scenario group with the name “all
scenarios” should appear underneath. You can now use this group (which is always present and
contains all existing scenarios and scenario groups) to define other scenarios and groups to any
nesting depth (see Figure 23). The following methods to create scenarios and groups are
available in a pop-up menu:
Right-click on a scenario group
Pop-up menu entry Function
“Add scenario into this group” A new scenario is created in the selected group
“Add scenario group into this group“ A new group is created in the selected group
“Insert scenario above this item“ A new scenario is inserted above the selected group (not
“Insert scenario group above this
item“
selectable for the scenario group at the top level)
A new group is inserted above the selected group (not
selectable for the scenario group at the top level)
Right-click on a scenario
Pop-up menu entry Function
“Insert scenario above this item“ A new scenario is inserted above the selected scenario
“Insert scenario group above this A new scenario group is inserted above the selected scenario
item“

TPT User's Guide Page 37
_
Figure 23: The scenario hierarchy
New scenarios are given the default name “scenario“; scenario groups are given the default name “group”
Scenarios or scenario groups can be deleted (see Deleting scenarios / scenario groups), moved (see
section 7.8: (Re)naming scenarios/scenario groups) or renamed (see section 7.8) whenever required
Each scenario that is created must of course also be “defined“. This process is described in detail in
Definition of Scenarios “Definition of Scenarios”.
7.7 Deleting scenarios / scenario groups
Scenarios or scenario groups can be deleted by right-clicking on the relevant name in the
scenario browser and then choosing “delete” in the pop-up menu (see Figure 23). If you delete
a scenario group, all the subordinate groups and scenarios are also deleted.
7.8 (Re)naming scenarios/scenario groups
There are two methods to rename an existing scenario or scenario group. Either right-click on
the relevant element in the scenario browser select “rename” in the pop-up menu (see Figure
23) or left-click, pause, left-click on the name of the element to be renamed.
7.9 Moving scenarios
You can change the order of scenarios and scenario groups within one scenario group by
moving them individually. Right-click on the desired element and select “Move scenario
(group) up” or “Move scenario (group) down”. The selected scenario or scenario group should
then be moved upwards or downwards by one position. The scenario element(s) may also be
moved using drag-and-drop.

Page 38 TPT User’s Guide
7.10 Commenting scenarios/scenario groups
Individual scenarios or scenario groups can be commented, just like testlets. To do this, select
the testlet that belongs to the scenarios to be commented in the scenario browser to choose.
Then enter comments in the documentation window (see section 1.2.4: The documentation
window).
Scenario groups can be commented in exactly the same way.
Right-clicking into the description window will open a popup menu which contains the option
“show inherited descriptions”. This will display the inherited description of the selected test
case. This inheritance is simply achieved by successively concatenating the descriptions of the
parent groups into a single description.
The comment itself is accessible (e.g. from the assessment or the report template editor) via
${scenario.comment}. The whole information of the inherited description can be
accessed via ${scenario.inheritedcomment}.

TPT User's Guide Page 39
8 Test set configurations
8.1 Introduction
Within different test-runs or different environments a subset of tests specified in TPT may be
executed. The test-set selection and configuration is done in the test set editor.
8.2 Selection of test-sets
The test set selection is accessed via menu item Execution / Configure test sets. Here test sets
can be assembled and named (see Figure 24).

Page 40 TPT User’s Guide
Figure 24: Test set editor

TPT User's Guide Page 41
9 Platform configuration
9.1 Introduction
TPT test cases are modelled independent of the execution platform. This means TPT test cases
can be executed in different execution environments. Each platform needs different
configurations in order to execute simulations.
In order to execute the tests the test platform has to be configured. The test platform is the
execution or simulation environment (e.g. Model in the loop (MATLAB/Simulink), standalone,
executable file or HiL). The specifics of the environment need to be specified in the platform
configuration.
E.g. the MATLAB platform requires information which Simulink-model file is used while HiLconfigurations
need information how signals at the HiL are mapped. For that reason for each
platform there exists a platform configuration.
Sometimes it makes sense to have different configurations for one physical platform. By doing
this a system under test can be tested in different environments like Model in the loop (MiL) or
Software in the loop (SiL).
9.2 Selecting the platform
Open a platform configuration window using execution | platform | add and select
the platform from the given list.
9.3 MATLAB/Simulink environment
One possible test execution configuration is implemented in MATLAB/Simulink. The test
execution engine (TPT Virtual Machine (VM) is implemented as an S-function in Simulink
(see Simulink S-function documentation). The S-function passes the values calculated by the
system under test (SUT) to the TPT execution engine. For each time step all outputs of the SUT
are inputs to the TPT VM. Thus all values that are needed for the test execution need to be
declared as inputs in TPT and all TPT-outputs are inputs into the SUT. The interface of the TPT-Sfunction
is defined by the channel declaration of the TPT testlet.

Page 42 TPT User’s Guide
When the MATLAB/Simulink environment is configured a MATLAB-version as has to be selected
and registered as a COM server (see Figure 25). Alternatively the so called RMI protocol can be
used for the communication with MATLAB. The RMI communication is the default
configuration.
The installed MATLAB-versions will be searched automatically by analysis of the Windowsregistry.
If this fails for some reasons the configuration can be done manually.
The MATLAB installation configuration can be either accessed via Platform configuration or via
menu “MATLAB/MATLAB installations ...”.
Please note that only one MATLAB-Version/Installation can be used at a time. In the case of COMcommunication
this version needs to be registered as COM-server.
In case of RMI communication MATLAB is accessed by default via TCP-IP-Ports 20556, 20557 or
3319. If for some reason these ports or not accessible alternative open ports can be used
instead. This can be configured using the checkbox in the “Setup MATLAB Versions” window.
(cf Figure 25). In case MATLAB is already open and runs a server on one of the given ports this
MATLAB is used by TPT an no new MATLAB is opened.
The MATLAB startup may consume more than 40s. In this case the “Startup timeout” can be
increased (cf Figure 25).
Figure 25: MATLAB version selection and registration
A Log-file and a startup directory may be specified (see Figure 26).
In the Log-file all communication with MATLAB is logged. The contents of the specified log-file
are the same that can be seen in the “Console”-view (cf. Figure 26).
The “Startup dir” is the directory MATLAB starts. In case MATLAB is already open and used TPT
doesn’t change the current MATLAB directory.

TPT User's Guide Page 43
Figure 26: MATLAB platform configuration
Test execution configuration
In the test execution configuration for a Simulink model file has to be specified. This consists of
the system model and the TPT virtual machine. Please note that this model file doesn’t have to
be generated manually. The test-frame may be generated automatically (see section 0: Original
model settings).
A TPT I/O-file needs to be generated. This M-file consists of the port definition and other
variables of the Simulink environment needed for TPT. This m-file is generated automatically
from the channel declaration (cf. Section 2).
The step-size (1/sampling rate) of the TPT-block needs to be specified (see Figure 27).
The step size is only valid for the TPT-S-function in Simulink and has no influence on the Simulink solver.
The timeout specifies the maximum simulation time. The simulation terminates after the
timeout value if it has not already terminated.
The history size field defines the number of samples that are held in memory and can be
accessed during test execution.
The content of the “Model load script” is generated automatically but can also edit by the user.
This script is run in MATLAB when the model is opened. The user can add proprietary scripts
and MATLAB function calls if needed.
In the MATLAB communication settings the user can specify how often MATLAB is restarted
during test-execution. This might be useful to avoid memory errors. Also it can be specified if
MATLAB should be kept open after the last test has been executed.

Page 44 TPT User’s Guide
Figure 27: Test execution configuration
Test run script
The test run script field describes the MATLAB-commands for the test execution of a single test
scenario. This script is generated automatically but can be changed by the user.
Environment variables
Environment variables are used to configure elements which apply to the MATLAB platform
configurations. Variables that apply to all platforms should be specified using
Tools|Preferences.
For example the variable “lightctrl.para” has the value “para_set1” in configuration
one and “para_set2” in the second (derived) configuration. Thus there are two simulation
environments with two different configurations for the same simulation platform. The
environment variables are accessed using: ${lightctrl.para}.
Console
The console shows all the communication between MATLAB and TPT.
Original model settings
The original model settings are only needed when the test frame is generated automatically.
They are not necessary for the test execution.
Here the model file of the system under test as well as the path to the block to be tested has to
be specified (see Figure 28). The model load script can be modified. The model interface (the
signal-names of the inputs and outputs of the system) can be imported from MATLAB. The testframe
can also be generated automatically.

TPT User's Guide Page 45
Figure 28: Original Simulink model settings
Import interface
The inputs and outputs of Simulink system can be imported (optional).
Figure 29: Import interface selection window

Page 46 TPT User’s Guide
Generate test frame
When the original model file is selected, the test frame for the test execution in MATLAB/
Simulink can be generated automatically (see Figure 30). Please note that the test frame
generation may fail due to user-specific configurations.
Figure 30: MATLAB/Simulink test-frame generation
This is done by creating a new model file connecting the TPT virtual machine execution block
and the original system model test block (see Figure 31).
Figure 31: MATLAB/Simulink test frame

TPT User's Guide Page 47
9.3.1.1 Execution details of the MATLAB-plattform
For the execution of test-models the execution procedure is as described in Figure 32:
close MATLAB
yes
connect to
MATLAB
exists MATLAB
connection?
restart MATLAB?
Figure 32: MATLAB test execution procedure
no
no
no
yes
no
Start test
execution
exists MATLAB
connection?
open test-model
all test executed?
End
yes
execute test
Connect to MATLAB
If no connection to MATLAB exists it has to be started. The start procedure is described in
Figure 33:
yes

Page 48 TPT User’s Guide
no
register COM server
starts MATLAB
exists Startup
dir?
run MATLAB script:
cd startupdir;
matlabrc;
run MATLAB script:
cd matlab_tpt_env;
init_tpt_env;
MATLAB already
connected?
yes
Figure 33: MATLAB start procedure
Start connect
MATLAB
COM
COM
vs
RMI
RMI
End
run Startup script
End
cd startupdir;
MATLAB aready
connected?
yes
no
no
exists Startup
dir?
cd MATLAB\work
run MATLAB.exe \r
run MATLAB script:
old = pwd;
init_tpt_env;
cd old;
Open Model
When initially the model is closed the model will be testframe model file will be opened and
the Model load script is executed.
Close model and MATLAB
The model and MATLAB close procedure is executed as follows:
bdclose all;
quit force;
By doing this the model is closed without saving potential changes of the model. Please note
that in the case of manual model changes the model needs to be saved manually.

TPT User's Guide Page 49
9.4 The executable platform
A very basic but flexible platform configuration is the Executable platform configuration. This
platform is any executable program that is specified.
In order to execute test cases the system under test (SUT) need to be stimulated by the
execution environment of TPT. The API of the TPT execution environment and how the SUT will
be connected to the TPT execution environment (TPT-VM) will be described in the following
section.
In Figure 34 the flow diagram of the executable environment is shown. The execution of the
test platform starts with an initialisation phase where the input file and the output file are
opened and the data for the stimulation are assigned to the TPT-outputs and the outputs of the
SUT are assigned to the TPT-inputs. The major loop consists of the actual periodical call of the
SUT and the TPT virtual machine for each time step. The test-procedure finishes with a closing
of the data files and a memory release. The return value of the executable must be set to zero
when the execution was successful.
Please refer to the lights control example and the “tpt_vm_api.h” where the full TPT-VM-
API description can be found. Please make sure having “tptvmapi.dll” in the same folder
as the executable.

Page 50 TPT User’s Guide
testcase.tvm
Start
tpt_vmapi_createExecution
tpt_vmapi_bindTestOutputToAddress
tpt_vmapi_bindTestOutputToAddress
tpt_vmapi_bindTestOutputToAddress
tpt_vmapi_bindTestInputToAddress
tpt_vmapi_bindTestOutputToAddress
tpt_vmapi_bindTestOutputToAddress
tpt_inputs = SUT(tpt_outputs,...)
tpt_vmapi_runCycle
test
end?
tpt_vmapi_closeExecution
9.4.1 TPT-VM-API for the execution platform
End
Figure 34: Flow diagram of the execution platform
testcase.tptbin
The functions of the TPT-VM-API are described in detail in the header file tpt_vm_api.h but
will be described here shortly.
tpt_vmapi_createExecution
This function initializes the execution of a TPT test-case given as a so called TVM-file. The results
of the TPT-execution are saved as TPTBIN-format.
tpt_vmapi_bindTestInputToAddress
This function assigns the output values of the system under test to the respective inputs to TPT.
tpt_vmapi_bindTestOutputToAddress
This function assigns the input values of the system under test to the respective outputs to TPT.

TPT User's Guide Page 51
tpt_vmapi_runCycle
This function runs a single time-step of the TPT virtual machine with given inputs and outputs.
This function need to be called in a loop together with the system under test function call.
tpt_vmapi_closeExecution
This function terminates the TPT runtime environment execution. It closes all open files and
releases allocated memory.
9.4.2 Executable platform configuration
Assume for example the lights control example is implemented as C-function that returns the
“headlight” as function of “light_switch” and “light_intensity”. In order to create
a test-frame for this a test-frame needs to be programmed and compiled that calls periodically
the TPT virtual machine and the function “getHeadlightValue”.
Templates for the executable platform generation are available and can be found in the lights
control example.
Figure 35: Executable platform configuration
For the Executable platform configuration please specify the working directory
(tpt.exeplatform.workdir) from where the command/function is executed. The
command itself consists of the executable function test-frame and parameters for the input-
TPT-file (tpt.scenario.tvmfile) and the output file (tpt.scenario.tptbinfile). In
the example the executable function is lights_control_testframe.exe in the working directory.
The parameter tpt.scenario.tvmfile, tpt.scenario.tptbinfile and
tpt.exeplatform.workdir are pre-defined variables used in TPT (see section 15.10:
Environment variables). Also the sampling time, the maximum timeout-time and the history
must be specified.
9.4.3 Test Source Code with the Exe-Platform
Before we begin to prepare, compile and test a given system’s source code using TPT and the
Exe-Platform, we have to ensure, that some prerequisites are met.

Page 52 TPT User’s Guide
• TPT has been installed with the “exeplatform” plug-in
• A Compiler/Linker for C-Code must be available
If both apply, we are well prepared for the following steps.
9.4.3.1 Build an Executable Test-frame
Each piece of software that is to be tested with the Exe-Platform must first be integrated with
the TPT-VM, which runs the test cases. This integration is called a test-frame and must be
provided as an executable file, so the Exe-Platform may access it.
TPT provides a wizard that generates the integration’s source code on the basis of some details
that have to be delivered by the user. It will work for all systems or system parts that conform to
a certain interface style that is often used with continuous system that has been implemented
using the C programming language.
In other words, the source code of the system to test must comply with the following rules:
• It has one interface function, implementing the continuous functionality to test
• The interface function must have an empty parameter list
• The interface function may not have a return value
• All variables, exchanged between the interface function and its adjacent system parts,
must be declared public within the global scope, so they are accessible for testing
Of course, the last point will implicitly apply in most of the cases, where the first three rules are
fulfilled, too. The following lines of code show a very simple example of such a function:
int value;
int factor;
int product;
void multiply()
{
product = factor * value;
}
If a function’s source code does not conform to this structure, it can most probably be adapted
to it by writing an adapter code.
When your source code matches the required structure, you may start to create the source
code of the executable that will run the tests on that function. If an installation of MS Excel is
available on your system, you may generate the needed source code with TPT.
If you do not have MS Excel installed, then you will have to write down the source code of test
executable manually. See SUT_main.c in the folder examples.
The “exeplatform” plug-in of TPT provides a mechanism that is able to generate the source
code of the test executable on the basis of a number of information that are read from an excel
file. In order to use this mechanism, create a platform configuration of type EXE-Platform and
click the button Generate excel interface file (cf. Figure 35).
After it has been created, the excel file will be opened, in order to let you specify the interface
of the function for which we want to create a test executable. We will now explain, how an
interface can be fully specified using the worksheets contained in the Excel file.
The Excel file created by the wizard contains three worksheets. One worksheet is used for the
general description of the function to call with its dependencies and two worksheets for the
specification of its input and output variables.

TPT User's Guide Page 53
For now, let’s concentrate on the first worksheet, which is named “General”. It contains four
fields that may be filled with information. The following table shortly describes each of them.
Label Semantics
Module name Optional. Takes a name for the generated module.
Custom imports Optional. If include statements are necessary to access the function to
adapt, they must be specified here.
Custom init Optional. If additional statements are necessary to initialize the
function before a test run starts, it can be specified here.
Function call Takes the source code that calls the function under test. The code,
filled in here, will later on be called cyclically during a test run.
The following screenshot shows an example of the worksheet filled out:
Figure 36: Function Specification with the Excel Sheet “General”
The next two worksheets, “Inputs” and “Outputs” both have the same structure, that allows a
user to specify a functions interface variables – or in words of TPT: its interface channels.
Figure 37: Interface Specification with the Excel Sheets “Inputs” and “Outputs”

Page 54 TPT User’s Guide
The first column takes the names of an input or output channel respectively. Note, that
channels may only contain alphanumerical characters and the underline. Due to this restriction,
channel names must sometimes differ from the source code’s original variable, e.g. if the code
variable is contained in a structure. In those cases, the variables original C-Code variable may be
stated in the second column. Furthermore you may specify the type of the C code variable.
The C-Code Type must be one of the following TPT C-code types which are equivalent to the
ANSI C-types which can be found in the table below:
TPT C-code type ANSI C-type
uint8 unsigned char
int8 signed char
uint16 unsigned short
int16 signed short
uint32 unsigned int
int32 signed int
int64 long long
float float
double double
bool unsigned char
The last two columns take optional scaling information for a given channel. It is assumed, that
scaling is applied using the polynomial form:
physical = fixed * slope + bias
When both, a slope and a bias are given for a channel, reading and writing that channel will
also include scaling values from its physical representation to its fixed-point representation and
vice versa.
Parameters that are to be accessed within the executable are configured in just the same way.
Have a look at the “Parameters” sheet, if you want to exchange and use system parameters.
As soon as you have filled the MS Excel Sheet with all information needed, you can return to the
Exe-Platform configuration dialog and use the button “Generate test driver C code”, in order to
finally generate a test-frame to the specified function. TPT will read in the Excel file and create a
C source file based on the information found.
You should now be able to build an executable file from the generated source code using an
arbitrary compiler and linker. If this fails, please also check, that all information you gave within
the Excel file are correct.
The resulting executable file is ready to be run with the Exe-Platform. Just configure the
platform with the correct command line and run your tests against the C-code.
9.5 Standalone platform
The standalone platform is not really a test execution platform because the system under test
will not be stimulated and no outputs from the system are inputs to TPT. The standaloneplatform
is more the execution of the test cases in TPT for debugging of the tests without
having the connection to the system under test. The inputs in TPT will be set to constant
default values. Thus this is more a simulation than a real test.

TPT User's Guide Page 55
10 Test Execution
10.1 Introduction
Tests can be executed after setting up test, test-configurations and platform configuration.
The test execution runs a test set on the different platforms.
10.2 Test execution configuration
Figure 38 shows the test execution configuration.

Page 56 TPT User’s Guide
Figure 38: Test execution configuration
Each configuration can be named and assigned to a test-set specified in the test-set
configuration. User defined attributes may be assigned to the configuration using the
“Attributes” tab. Use the “Run” button to start a test execution. By using the “Refresh” button
you can recompile your TPT model.
Data directory
A data directory where all relevant test data is stored needs to be specified. The data structure
also needs to be specified. Options given are to use a flat or tree structure based on an index or
scenario ID.
Reference directory
The test results may be compared with reference data from earlier test runs. The path to the
reference data needs to be specified. Within the report the appearance of the data needs to be
specified. The data can also be used within the assessment.
When the data dictionary is ${tpt.tptfile.dir}\TPTdata\ the reference directory could be
${tpt.tptfile.dir}\RefTPTdata\Stand_alone_test_engine when the former
execution was done using the stand alone test engine.
Reference root
Choose if the reference directory is the main execution directory or a platform directory.
Report directory
If you choose to create a report after the execution, you have to specify a report directory first.
All report data will be written into this directory.
Report format
There are currently 2 possible report formats available: HTML and PDF. If you request to
generate a HTML report, you can view it with a custom web browser; PDF reports can be
viewed with a PDF viewer.

TPT User's Guide Page 57
Platforms
The platforms upon which the test shall be executed need to be selected from the platform
configurations specified before.
Which steps are executed have to be selected. Use check boxes for execution, debugging,
assessment and report generation.
The build process is started by using the “compile & run” button. Once the execution begins a
window opens which gives an overview over the progress of the process. Please note that only
the test cases or scenarios selected in the testlet or scenario browser will be executed.
10.3 Pauses or “Intermission points”
Figure 39: Build progress window
Breakpoints will pause the test execution for a certain period of time. To insert a pause rightclick
on the test cases (or the scenarios) before which you want to halt the execution. Select the
“intermission point…” item from the pop-up menu and then insert the message which should
appear if the pause is reached. You may also state how much time should pass until the
execution resumes (in the “intermission point timer value” field, see Figure 40). Finally, the
“enable intermission point” check box needs to be activated so that the “intermission point” is
activated.
Active intermission points are identified by a red dot above the respective scenario symbol in the scenario
browser.
Intermission points are only active in test cases or scenarios which are passed to execution.

Page 58 TPT User’s Guide
Interminssion point marking
Figure 40: Intermission points
Intermission point configuration

TPT User's Guide Page 59
11 Test Analysis
11.1 Introduction
Once executed, test results in TPT can be analyzed by either using the built-in Test Data Viewer
or by generating a comprehensive HTML report. The following section will give you a brief
overview of both options.
For qualitative and quantitative test result evaluation please see TPT assessment manual.
11.2 The Test Data Viewer
By using the Test Data Viewer, the tester can analyze each channel of the whole test run. The
input of the Test Data Viewer is a file in TPTBIN format, created after a test has been executed.
You can also use the Test Data Viewer to display the results of the test assessment or
measurements of different formats like .mat, .mdf, .csv.
To open the Test Data Viewer you can either choose it from the main menu Tools > Test
Data Viewer or you use the context menu of the Build Progress Window (Figure 40).

Page 60 TPT User’s Guide
Figure 41: Opening the Test Data Viewer from the Build Progress Window
The Test Data Viewer features a table containing all signals of the current test execution on the
left and an arbitrary number of customizable view panels used to depict the values of a signal
over time on the right. You can display a signal by simply dragging it from the signal table to
the desired panel or by selecting the signals checkbox.
Two axes with different scale maybe displayed in the same panel. A signal can be displayed in
the right axis by dragging the signal to the right axis. The scales can be zoomed and scrolled at
the respective axis scale.
Multiple axes can be generated either by choosing it from the main menu View > Add
view above/below or by the use the context menu of the axis.
Figure 42: The Test Data Viewer

TPT User's Guide Page 61
A toolbar and a context menu with some useful functions for test analysis are provided. It can
be selected between different view modes such as select mode, zoom mode, move mode but
also a sample point table can be displayed:
Selection Mode
By using the Selection Mode, you can click on a desired point within the timeline and the exact
value of each signal at that point will be displayed in the Value column of the signal table. The
value can be displayed in binary, decimal and hexadecimal format. The format can be changed
by right-clicking on the value.
Sample point display
Sample points are the moments in time, for that a signal has a concrete value. The space in
between 2 sample points is interpolated. If you are interested in looking at the sample points of
a signal, do so by simply enabling Show Samples in the menu.
Note that you will most probably have to zoom in to see the single sample points of a signal
Switching Interpolation Modes
The Test Data Viewer provides different algorithms for displaying the space between two
sample points of a signal. You can choose linear or last value interpolation. If you just want to
see the raw sample points, you can also disable interpolation.
Change time synchronisation model
The Test Data Viewer provides different time-modes for displaying the signals. The view can be
switched between TPT-synchronous mode and SUT-synchronous mode. TPT measures it’s in-
and outputs. In the case one looks form TPT it is called TPT-synchronous mode and when the
inputs are one time step delayed, compared to the output the view is synchronous for the SUT.
11.2.1 Test data viewer operational modes and shortcuts
Some short-cuts are available within the different modes. Some are valid in all modes but some
shortcuts are available only in special modes:
Generell Features (in all modes)
CTRL + LEFT/RIGHT/UP/DOWN: scroll
CTRL + Drag Mouse-Left: scroll
Click Mouse-Right: Context menu
Mouse-Wheel on Diagram: Zoom in/out
Mouse-Wheel on X Axis: Zoom in/out X-axis
Mouse-Wheel on Y Axis LEFT/RIGHT: Zoom in/out Y-axis LEFT/RIGHT
Select/Edit mode
LEFT/RIGHT: move the time cursor
Click Mouse-Left: Select signal/sample(s)
Drag Mouse-Left: Select sample(s)
Zoom mode
Click Mouse-Left: Zoom In
Shift + Click Mouse-Left: Zoom Out
Drag Mouse-Left: Zoom to Region
LEFT/RIGHT: n/a
CTRL + LEFT/RIGHT/UP/DOWN: scroll
Move mode
LEFT/RIGHT: n/a
CTRL + LEFT/RIGHT/UP/DOWN: scroll

Page 62 TPT User’s Guide
11.3 The HTML Report
While the Test Data Viewer allows you to dig into the details of one single test execution, the
TPT report provides the big picture of the whole test run. This report serves as a comprehensive
and highly configurable HTML summary with interactive diagrams similar to the Test Data
Viewer.
A TPT report is created using a customizable Report Template (for more details on report
templates refer to chapter ‘The Report Template Editor’).
To create a report for a test execution, choose the desired template and enable the Report
option in the execution configuration dialog (Figure 43: Report option in the Execution
Configuration Dialog).
Figure 43: Report option in the Execution Configuration Dialog
After all tests have been executed, you can display the test report by clicking the Open Report
button in the Build Progress window. The report will be opened with your default browser.
Figure 44: Report overview in Mozilla Firefox depicts the report overview, from which you can
start browsing into the details of any executed scenario.
Figure 44: Report overview in Mozilla Firefox

TPT User's Guide Page 63
11.3.1 Report overview
The report overview contains useful information about the whole test execution. This overview
starts with general information which includes an execution summary and a small meta
information table.
The execution summary shows the total number of executed tests and gives a detailed
overview of the results that were observed (total number of succeeded, failed, indifferent and
execution errors).
The meta information just contains the filename of the corresponding TPT file, the name of the
execution configuration and the total number of executed scenarios.
This information is enriched with a per-platform overview which includes another summary
table, an overview of the executed scenarios and an overview of the assessment variables with
their respective name and result information.
Clicking on a scenario in the “platform overview” will open the scenario-specific report (this is
equal to clicking the scenario on the platform overview which is visible on the navigation bar
on the left hand side of the report).
Clicking on an assessment variable in the “variable overview” will open an overview report for
the selected variable. This is useful in order to investigate the status of a specific assessment
variable across all executed test cases.

Page 64 TPT User’s Guide
12 The Report Template Editor
12.1 Introduction
Templates control the content and the layout of reports created by the report generator. In the
current TPT version, the report generator has the ability to create such reports in HTML format.
As well as a template file the report generator needs a set of test run results in the form of
signal waveforms and variable allocations. The following chapters deal with the creation of a
template using the template editor.
Templates, in their internal representation, are XML files. In order to be able to generate a template you
can either use the template editor or you can write the template “manually” if you are familiar with the
XML structure.
12.2 Creating a template by means of the template editor
The template editor is a tool which you can use to build your own control templates
interactively. Open the editor by selecting “template editor” in the “tools” menu or by the
Ctrl+T hotkey. The template editor window is divided into two halves (see Figure 45). On the
left-hand side the template structure is depicted as a tree, while the right-hand side of the
window shows the properties of a template statement selected in the tree.

TPT User's Guide Page 65
Figure 45: The template editor
When the editor is started, the template window contains one root statement, which is named
“test report” by default. Right-clicking brings up the context menu containing all template
statements which can be added to the template. For example, if you select “create section”, a
section statement will be created within “test report”. The entire tree structure of the template
is built up in this way.
It is also possible to insert statements by using the toolbar of the template editor.
It is possible to delete any statement (bar the root statement) in the tree by right-clicking on a statement
and selecting “delete element”. Please note that all statements nested within the deleted statement will
also be deleted.
Properties may be assigned to every statement in the template tree. For any selected
statement, the corresponding entry fields appear in the right-hand side of the window. Due to
the multitude of properties, we will only mention the most important ones here:
Statement Properties which should be assigned
Section The title of the section should be entered in the “Title” field. The “Identifier” is an
optional parameter which can be referred to from the assessment script.
Paragraph The paragraph-test of the section should be entered in the “Text” field. Please note
that variable-names can be used e.g. “${scenario.inheritedcomment}”. The
“Identifier” is an optional parameter which can be referred to from the assessment
script.
Select On the “details” index card in the “filter” field a regular term/expression for the
channels has to be entered, which “matches” the elements in the scope to be
Conditional
Execution
selected. Also a subset of channels can be excluded using check-boxes.
On the “details” index card a variable name of type Boolean has to be entered into
the “Expression” field, whose value in the selection should be checked for. The
successor statements will be executed if the “true” value has been selected in the
“value” drop-down menu and the given Boolean variable exists in the selection. If
“false” has been set, the reversion applies.
For Each Over all elements will be iterated which have been selected before using “Select”.
The order of the execution can be chosen by selecting a sorting criterion.
Channel table On the “details” index card a table header should be entered into the
“header”“subtitle” field.
Parameter table On the “details” index card a table header should be entered into the
“header”“subtitle” field.
Signal graphic The graphic should be named in the “subtitle” field. Also axes-properties can be set.

Page 66 TPT User’s Guide
Important properties of template statements
The layout of all reports may be defined globally by selecting “Tools” see “Default editor”. The
window now displays the layout properties of the global report.
Most of the properties, which are determinable at statement level or which concern the global layout,
have not been described in detail. All properties provide information about their usage via the “tooltip”
feature which appears when the cursor hovers over the property.
12.3 Loading and saving a template
Loading and saving templates is done normally in the “file” menu of the template editor.
12.4 Elements of a template
The Report Template statement
The Report template defines the Title and style of the report. An XHTML-style-sheet can be
selected and modified.
The Meta information statement
The Meta information statement inserts the meta-information of the test execution like filename,
number of scenarios etc.
The Meta information statement is optional and can only appear before all other statements.
The Table of Contents statement
The Table of Contents statement inserts a table of contents.
The TOC statement is optional and can only appear before all other statements.
The Table of Figures statement
The Table of figures statement creates a table and graph directory (table of figures).
The TOF statement is optional and can only appear after the TOC statement or before all other
statements.
The Section statement
The Section statement creates a named section or subsection.
The Select statement
The Select statement selects a subset from the set of all variables. The reason for selecting a
subset of all variables is to reduce the report to information of interest only.
Selects may be nested in any desired way. If a subset of variable is selected only those are
accessible within this Select-statement. Using regular expressions the content of the select
filter can be chosen. Also check-boxes for the exclusion of information are available.

TPT User's Guide Page 67
Figure 46: Template Editor Select statement
For example the term “[^_][^r][^e][^f]$” in the name filter filters all names with “_ref” at the
end.
The For Each loop statement
The For Each statement implements a loop which encompasses each element of the set of
variables. For example a run over selected channels executes the statements within the loop
which perhaps is already restricted by previous Selects. A For Each executes one implicit Select
of exactly one element in each iteration of the loop.
The order of the execution of the loop can be controlled by using “Sorting”. Items can be sorted
by name, type etc.
Figure 47: For each loop template editor

Page 68 TPT User’s Guide
The For Each statement can be positioned anywhere, but has to have an (arbitrary) successor (exception:
TOC and TOF).
The Conditional statement
The Conditional statement has the effect that all successor statements are executed only after
they have fulfilled a certain condition (Expression).
The Conditional statement can be positioned anywhere, but has to have an (arbitrary) successor
(exception: TOC and TOF).
The Channel table statement
The Channel table statement draws a table. All variables which are selected in the currently
select-statement are entered into the table. The order of the entries can be sorted e.g. by name
or type.
The Channel Table statement can be positioned anywhere, but must not have any successors.
The Signal graphic statement
The Signal Graphic statement graphs a signal form. In the graph all variables are entered which
can be found in the currently selected set of test runs, scenarios and variables.
Abbildung 48: Signal graphic report template
The Signal Graphic statement can be positioned anywhere, but must not have any successors.

TPT User's Guide Page 69
13 Function Wizard
13.1 Motivation and targets
Through direct definition testlets TPT offers the possibility of describing a complex waveform in
the form of a function expression. TPT provides a wizard for selection of simpler functions.
13.2 Access to the function wizard
The function wizard can be opened if TPT displays a direct definition testlet and exactly one
entry is highlighted.
Figure 49: Opening the function wizard

Page 70 TPT User’s Guide
13.3 The individual functions
The function wizard assists in the generation of the following functions: constant value, ramp
functions, asymptotic functions and periodic functions. The function is valid while the state is
active.
13.3.1 Constant function
The constant function assigns a specified value while the state is active. This value is defined by
either the last value of the prior state or can be set explicitly.
13.3.2 Ramp function
Figure 50: Constant function
The ramp function rises or falls linearly to a target value over a specified time or with a specified
gradient. The start value can either be stated explicitly or taken from the prior state.

TPT User's Guide Page 71
13.3.3 Asymptote function
Figure 51: Ramp function
The asymptote function converges to the “Target Value” and approaches the target value in
approximately “duration” time. The beginning of the time dependent function is either
continuous, continuous differentiable or as specified with start value and gradient. If
continuously differentiability is chosen the differentiability is taken from the last two values of
the prior state.
13.3.4 Periodic function
The periodic function oscillates between two values (floor & ceil). The oscillation can be
specified by either period (t) or frequency (1/t). The saw-tooth wave does not need any further
parameters, the rectangular wave and the triangle wave can be weighted via the “proportion”
(mark space ratio) within an oscillation.

Page 72 TPT User’s Guide
Figure 52: Periodic function

TPT User's Guide Page 73
14 Debugging of Test Automatons
Test-case models built with TPT can form very complex and comprehensive automatons. If the
behaviour of an automaton differs from the expected behaviour or if a runtime error occurs,
retrieving the cause of the observed behaviour may be quite difficult. The interaction of a large
number of external elements and values provided by the system under test, and it’s the
complex environment can make it virtually impossible to trace and analyze an automaton’s
behaviour without the appropriate tool support.
With this in mind TPT comes with a plug-in, that serves the sole purpose of tracing and
analyzing an automaton’s runtime behaviour and hence provides support for systematic
debugging.
This plug-in enables a user to precisely trace a test case’s execution. In doing so just looking
closely at the test results will usually– and especially for complex test automatons – help very
little. Instead more detailed information about the internal state of the automaton at a certain
point of its execution is often needed, for example, to analyze state transitions and their
“timing”. This could be achieved by step-wise execution of the automaton. However, since
running a test case automaton may require several thousand execution steps, the debugging
provides several features to analyze one or more states of a paused automaton, to examine and
analyze its internal state.
14.1 Basic modules of debugging
It is a fundamental characteristic of TPT that test cases are described independently of a specific
test environment to run on. This does not only apply to modelling a test case but is used for
execution as well. To achieve this the TPT execution machine (TPT-VM) may easily be integrated
with various proprietary simulation tools and environments. However, proprietary platforms
often impose restrictions that limit the control over a test case’s runtime. A typical restriction is
that the execution of a test case may not be paused.
Therefore the process of debugging a test case is carried out in two separate steps: First, the
test case to be debugged is executed on its target environment as usual. Then the recorded
data will be used to execute the same test once again. This time however, “offline” using the
stand-alone execution environment which comes with the TPT-VM. The system under test as
well as the test case’s execution environment will be simulated using the recorded data.

Page 74 TPT User’s Guide
This method is called capture & replay and, besides providing independence of the target
environment, provides an additional advantage: a test run may be “debugged” repeatedly on
the basis of a single test execution. This can save a lot of time.
As in conventional programming languages it is possible to use a breakpoint in TPT to
interrupt a test driver in its execution after reaching an internal state of the automaton specified
by the user. Breakpoints may be added or deleted during the runtime of a debug session.
As soon as the breakpoint has been reached all currently active states of the automaton are
displayed. This also applies to all automatons that are used within the currently debugged test
scenario. Thus, following conventional programming environments, all elements starting from
an active state and describing a path through the automaton hierarchy up to its root can be
understood as a stack-trace.
To continue stepping through the interrupted test execution the user may
• Resume the execution for one discrete step in time (step cycle).
• Resume the execution until the next state transition (step over).
• Unconditionally resume the test execution (resume).
The execution of a TPT automaton may be stopped by the user at any time.
14.2 Debug plug-in features
The debug plug-in complements the application by supplying additional functionality needed
for debugging. These extensions can roughly be divided into two sections: extensions to the
user interface for modelling automatons or test cases and extensions to the test execution
process to facilitate debugging of the execution.
14.2.1 Extensions to the user interface: definition of breakpoints
The set-up and the semantics of breakpoints are defined as follows:
• A breakpoint must be defined within the context of an automaton. This may be the
root testlet.
• A breakpoint must be defined within the context of a scenario or a scenario group. If
no scenario has been selected the default group of “all scenarios” will be used.
• A breakpoint which is defined at the scenario group level applies to all scenarios and
scenario groups contained therein. This mechanism is called inheritance or
propagation of the breakpoint.
• A trigger is the event which activates a breakpoint. There are trigger variants “on
entry” and “on event”. The trigger variant “on entry” lets the breakpoint become active
every time the execution of the test reaches the set state. In the trigger variant “on
event” a condition also has to be logical “true”. The condition has to be stated in the
“event” column and follow the syntax of TPT.

TPT User's Guide Page 75
Figure 53: Table view for the creation of breakpoints
The definition of the breakpoints takes place in the “debug” tab. It is possible to define
breakpoints just for the selected combination of testlet and scenario. If the selected testlet is an
automaton it is also possible to define additional breakpoints for the states/testlets that it
contains.
Thus, for most testlets of an automaton there are two locations at which a breakpoint may be
defined: at the respective testlet itself or within the context of the super-ordinated automaton.
Here the difference cannot be found in the definition of the breakpoint condition, but by
considering which scenario this breakpoint has been defined for. If a breakpoint for a testlet…
… is created directly in one of the testlet’s scenarios, it is then defined for all super-ordinated
application sites. This location should be selected if a breakpoint defined for the testlet
should be effective in each scenario of the super-ordinated automaton or each use of a
certain scenario of this testlet.
… is created indirectly in the context of the super-ordinated automaton, the definition of the
breakpoint may be restricted to scenarios of the super-ordinated testlet. A breakpoint
should be defined here if it is only of interest to a certain scenario of the super-ordinate
testlet.
If a breakpoint is not defined within the current scenario but has been propagated down to the
current scenario, its definition location is linked in the “inherited from” field.
14.2.2 Finding breakpoints
Scenarios and testlets with breakpoints display a red triangle in the upper left-hand corner. The
semantics of a solid or outlined triangle differ in the testlet browser, the scenario browser and
the modelling window.

Page 76 TPT User’s Guide
Figure 54: Depiction of breakpoints within the tree and automaton view
In the testlet browser a solid triangle means that all scenarios of this testlet have a breakpoint.
This may be because either all scenarios have their own breakpoint or a breakpoint has been
defined at the group level for all scenarios. An outlined triangle in the testlet browser means
that at least one of the scenarios (but not all) contains a breakpoint.
In the scenario browser a solid triangle in a scenario or a scenario group indicates that a
breakpoint has been defined in this scenario or scenario group. Outlined triangles mean that
this scenario “inherited” a breakpoint from the hierarchy of the scenario groups. Each
breakpoint created at a scenario group is valid for all scenarios beneath its level in the tree
hierarchy.
In the modelling window a solid triangle means the displayed combination of testlet and
scenario possesses its own breakpoint, in the case of an outlined triangle the breakpoint is
inherited. Furthermore, testlets which have sub-testlets with a defined breakpoint are provided
with an additional outlined triangle.
14.3 Executing a test for debugging
Each completed test execution can be “debugged” immediately, independent of whether or
not the corresponding automaton possesses a breakpoint.
14.3.1 Configuring the execution of tests in debugging
In order to start a test execution in the debug mode starts by opening the dialog for the
configuration of a “build” as usual and check the ‘debug’ box (see Figure 55).

TPT User's Guide Page 77
Figure 55: The "build" dialog
Similarly to the “assessment” and “generate test report” steps it is possible to start debugging
without executing the test. In this case the system searches for and uses a previous test report.
Therefore once a test case has been executed it can be repeatedly “debugged” with a minimum
of time and effort.
Attention! Caution is recommended when using this mechanism because: An automaton should be
debugged solely on the basis of its own execution results. If the test data used in the debugging has been
recorded from an earlier version of the same automaton or even from a completely different test
automaton it will lead to unpredictable behaviour of the application.
To highlight this risk a warning will be displayed if a debug session is started without a report
from a previous execution.
After the build process has been configured and its execution has been started progress is
displayed as normal: compilation, test execution, test evaluation, and report.
14.3.2 Sequence and operation of an execution during debugging
The progress dialog disappears once the debugging of a test execution begins, while the main
window comes to the foreground. The scenario forming the basis of the test execution is
displayed and all other scenarios which are not used within the test-run, are greyed-out in the
tree views. Additionally, a group of three “floating” debug windows become visible.

Page 78 TPT User’s Guide
Figure 56: The user interface of the debugging runtime
These windows always stay on top of all other windows. All interactions with the other
windows remain available.
Consequently all functions available in TPT remain accessible during debugging. Deletion or
addition of breakpoints can take place during the debug runtime of a test as during modelling
time through the table view within the debug tab (see Figure 56). Navigation through the
overall automaton using the testlet and scenario trees on the left hand and the automaton
view on the right-hand remain available.
14.3.3 The “control debug session“ window
The dialog with the title “control debug session” provides execution control of the test. The
options are “pausing”, “resumption” or “terminating the execution”, as well as the “stepping”
functions “step cycle” and “step over”. Two more buttons control the fading in/out of the two
additional “channel watch” and “breakpoints overview” windows. The speed of the test
execution can be controlled by using the scroll-bar displayed at the bottom of the window.
The following overview provides a brief overview over the buttons available and their meaning:
Prompts the resumption of a paused test execution (“resume”).
Stops an ongoing test execution (“pause”).
Terminates the test execution and thus the debugging (“terminate”).
Continues a paused test for exactly one execution step (“step cycle”).
Continues a stopped test until the active state changes (“step over”).
Activates/Deactivates displaying the “channel watch” window.

TPT User's Guide Page 79
Activates/Deactivates displaying the “breakpoints overview” window.
As soon as the test execution has been stopped, either by reaching a breakpoint or by using the
“pause” function, the debugger highlights all active states of the selected automaton in red. If
one changes the selected state or automaton the highlighting is refreshed according to the
new context. This makes it possible to inspect the executed states of all sub- automatons.
Knowing about these highlight markings it is now possible to explain the “step over” function
in more detail. As can be read in the table presented above, it “continues a stopped test until
the active state changes”. It remains open which active state of the overall automaton is meant.
After all, in most large automatons at almost every point of their runtime many states are
executed and are thus active. Knowing about the highlight markings described above it is now
possible to give a simple and retraceable answer:
The step over function refers to the active states of the automaton which at the moment of triggering
this function is selected and displayed. Using it, the paused execution will be continued until a state
transition takes place.
The slide control controls the execution speed from left (slow) to right (fast).
If the execution speed is set to the maximum, updating the displayed runtime data (channels and
variables) is reduced. Consequently signal values being viewed at execution time are no longer updated
despite the debugging.
Setting the slide control to the maximum speed thus only makes sense if the aim is to reach an
advanced point of the test execution in the shortest amount of time possible, avoiding parts of
the test which are not interesting for debugging purposes.
14.3.4 The “channel watch” window
Information about the internal states of the corresponding automaton are collected during the
entire execution and displayed in this window. Among them are the time that has passed in the
executing automaton (global time) as well as the current values of each channel and variable of
the automaton. Moreover, these values are displayed in diagrams at the right-hand side of the
table. To display a signal in the viewer, select it from the table and drag it onto one of the
displayed viewers or use “add signal” in the context menu.
14.3.5 The “breakpoints overview” window
The “breakpoints overview” window contains a table view which lists all breakpoints of the
recently executed automaton. During a test execution all breakpoints are depicted in grey.
Only when the ongoing execution is stopped by one or more breakpoints, the breakpoints that
caused the test execution to stop are depicted in black and are moved to the top of the table.
A breakpoint definition location can be displayed by double-clicking on its row in the table.

Page 80 TPT User’s Guide
15 Further TPT functions and tools
15.1 TPT help system
Access the context-sensitive help system by pressing Ctrl+F1 or selecting Help | Help
from the main menu. The TPT help system will detect your current working environment and
display the corresponding help topic.
TPT organizes the help contents in a library which consists of help books. The individual books
can be viewed by selecting the desired book in the Help | Help Books menu.
When writing assessment scripts the context-sensitive help system will detect the identifiers at
the current cursor position (or the selected function in the auto completion) and display
valuable information about it.
15.2 The search an replace function
The search function locates all occurrences of a certain character string (word or phrase) within
all expressions or channel names of the currently shown test model. It can be reached via
Tools | Search or its hotkey Ctrl+F,
Once this function has been selected, a search string dialog opens. Additionally the two check
boxes below the text search field may be used to determine whether the input is a regular
expression and whether it is to be treated as case sensitive or not (see Figure 57).
The search results are grouped by their location and displayed below the input area of the
dialog.
The results will include all occurrences of a given character string within the filtered contents of
the TPT-file (see Figure 57). Double-clicking on a single search result within the tree view will
cause TPT to show this context and select it.

TPT User's Guide Page 81
Figure 57: The search window
15.3 The history function
All navigation is stored by the history function. This allows a user to navigate backwards and
forwards; re-selecting the previous testlet or scenario. In other words, it works just like a typical
web browser’s ”back” and “forward” buttons.
Both functions can be found in the toolbar which are shown with an arrow pointing to the left
(“navigate backward”) and another pointing to the right (“navigate forward”).
15.4 Auto-completion
When working with declared parameters, constants or channels at a textual level within TPT,
the auto-completion provides easy access to all declared names available for the given context
(see Declaration of Channels, Parameters and Constants ).
The auto-completion feature is triggered using the hotkey Ctrl+Space from within either
the assessment editor or the input fields used for defining the equations of a “direct definition”
testlet. A pop-up window opens up at the cursor’s current position. This contains a list of the
available declared names. An entry from the list is selected using the mouse or cursor keys and
hitting ENTER .
If you know the first few letters of the declared name, enter them into the input field or the
editor then trigger the auto-completion. The auto-completion tries to match the text to a
declared name. Matching text can still be edited when the pop-up is present. You can always
cancel auto-completion and close the pop-up window using the ESC button.

Page 82 TPT User’s Guide
The auto-completion feature will always try to complete a word beginning to the left of the cursor
position. Such a partial word is detected when alpha-numerical characters are found directly between the
cursor position and the first space character left of the cursor position (or the left boundary). Therefore,
the pop-up window of the auto-completion will only show all declared names, if the cursor is at the line
start or follows a space character.
15.5 Menu Options
Some options for the graphical editor can be reached via the menu Options.
Smooth Lines and Text
This option is used for smoothing the graphical representation of the automatons in the main
window.
Scroll Automatically
This option can be used to move objects over the border of the visible area in the main
window. Assume one would move a state using drag and drop. When Scroll Automatically is
activated the visible area in the main window moves with the moving object.
Show Overlay Info
This option shows the information that is associated with transitions in the main window.
Show Tooltips
When the Show Tooltips option is active and the mouse dwell at a transition or state additional
information is shown.
Image Resolution
The option image resolution configures the resolution of the image that can be exported via
menu Edit/Save Image...
15.6 Interface import
This function offers the ability to import all types of declarations from either a TPT file or several
other file formats and, optionally, applying them to the signature of the currently selected
testlet. It is initiated by using Tools | Import Interface Signals from the menu. A
dialog containing a wizard will open which guides you through the subsequent steps (see
Figure 58).
Figure 58: Interface import

TPT User's Guide Page 83
15.7 The logging server
15.8 Statistics
The logging server, which can be started via Help | Start Logging Server (or its
hotkey Ctrl+L), only provides access to TPT’s internal messages and is mostly irrelevant to
users. But in case you experience problems with TPT, your TPT support contact may ask you to
start the logging server to examine the messages.
The statistics plug-in has been developed to provide the tester with an overview of the
spreading of test cases. It shows how often states of a testlet, specs of a transition and
transitions of a path have been used and how often it was combined with each other. A path is
an intersection of transitions going out a testlet (see Figure 59), so there are different
possibilities for the automaton. The different transitions of such a path can be seen like states in
a testlet.
Figure 59: Example for a path
It might be important that all defined scenarios are used in order to reach certain test coverage
as broad as possible. For this, the statistics plug-in (which can be found in the menu item
“Tools”) creates an overview for the currently selected testlet in the form of a table (see Figure
60).
The following subsections will illustrate the four columns in detail on the example of a testlet.
The meanings for transitions and path are analogue.
Figure 60: Statistics for "Test of lights control"

Page 84 TPT User’s Guide
15.8.1 First column – Object overview
The first column contains a tree, which shows the hierarchy of all the testlets, transitions and
paths in this order. Each object has the two nodes “variants”, which lists all the variants of an
object, and “pairs”, which contains a list of all other testlets, transitions and paths.
A completely opened testlet-node can be seen in Figure 60, number 1.
15.8.2 Second column - Amount
The second column simply displays the amount how often a testlet and its states were used in
all scenarios. The percentage can be read of the size of the bar, which relates to the total
number of scenarios (see Figure 60, number 2).
15.8.3 Third column – Spreading of variants
To see whether tests are distributed well TPT analyses the coverage of all states in a single
testlet. Therefore TPT calculates the “distance” between the current spreading and the optimal
possible arrangement with the amount of the testlet.
The example (see Figure 60 number 2/3) shows that the testlet ”changing light intensity” is
used six times. In detail: one state is used four times; the second two times and the three
remaining are never used. The optimal arrangement with five states and six available would be
one state two times and every other state once.
Similar to the process of standard deviation TPT calculates in this case a value of 2.8. The
appropriated green bar relates to the worst calculated value of all objects.
15.8.4 Fourth column – Spreading of combinations
To evaluate the coverage it is also important to consider the combinations of two objects. To
realize the importance an example: two testlets can be good in the sense of the second column
but state 1 of testlet A is only used with state 2 of testlet B. To cover such problems TPT also
calculate a value for the combinations of objects.
The relation between two objects and its variants can be described by a matrix which contains
the amounts of a state in combination with every other variant. Similar to the spreading of
variants TPT calculates the “distance” between this matrix and the best possible distributed
matrix with the same total amount. This value is now called the distance between two objects
(see Figure 60, number 5).
Out of all the distances the average distance of a testlet is made and shown in the fourth
column (see Figure 60, number 4). The bar again is related to the biggest distance between two
objects. In addition the blue line over the bar shows the minimum and maximum distance from
this testlet.
15.9 Restore from history
TPT automatically saves a copy of the currently open file at regular intervals if it has been
changed. A backup is created every five minutes by default or when the user saves the file
manually. By default a total of twenty backups are kept and may be restored.
To restore a backup, use the menu item File | Restore From History. There, you will
find an overview, listing all saved backup files along with their backup time and information
about whether the save operation has been performed manually or automatically. To restore a
backup file, select the desired backup time in the list and use the “Restore” button.

TPT User's Guide Page 85
15.10 Environment variables
Environment variables can be used to customize settings for storage, execution, and meta-data
in TPT. To name some examples: global settings of particular directories, installation paths,
project names etc. can be stored as environment variables. There are predefined environment
variables and user defined environment variables. Environment variables are handled by TPT by
means of simple text substitution. There is no semantic analysis of environment variables done
by TPT. Environment variables can be seen as “configuration place holders” that help to
separate invariant settings from variant parts.
Environment variables can be used in file paths, names, scripts etc. using the
${variablename} convention. For example “${tpt.tptfile.dir}/myfile.txt”
addresses a file myfile.txt in the same folder as the current tpt file (see section 15.10.2 for a
description of environment variable tpt.tptfile.dir).
In some cases environment variables do not exist. You can use a default substitute if you want
to handle these situations manually: “${tpt.tptfile.dir?TEMP}/myfile.txt” will
deliver “TEMP/myfile.txt” if the variable “tpt.tptfile.dir” does not exist, since
“TEMP” is the default substitute.
15.10.1 Definition of environment variables
Environment variables can be defined at three different levels:
Global environment variables are defined independent of the TPT model files globally in the
context of the TPT installation. More precisely, global variables are stored in the global
tpt.config file which is stored in the folder /Local/TPT. The purpose of
global variables is to specify machine specific settings that are not dependent on the TPT
model but on the machine properties such as installation paths, project paths etc.
Model specific environment variables are defined specific for a TPT model file. The purpose of
model specific environment variables is to define common attributes that can be shared at
different places within the TPT model such as the name of a project, version numbers etc.
Platform configuration specific variables are defined in the context of a concrete platform
configuration. Platform specific variables can be used to fine tune the platform configuration or
in conjunction with derived configurations.
Environment variables can be overwritten with the precedence global < model < configuration.
In other words, model specific variables can overwrite global variable settings and platform
configuration variable settings can overwrite model and global settings.
The following environment variables are predefined automatically by TPT.
15.10.2 Execution Configuration variables
Name Format Description
tpt.testdatadir dir Directory where to store the data collected at compilation, runtime,
assessment, and reporting tests
tpt.tptfile file The filename (complete path) of the current tpt file.
tpt.tptfile.dir dir The directory containing the current tpt file.
tpt.date text current date in format YYMMDD
tpt.time text current time in format HHMMSS
tpt.rootdir dir Installation path of TPT

Page 86 TPT User’s Guide
15.10.3 General platform configuration variables
In addition to the environment variables stated above, the following environment variables can
be used in the context of platform configurations:
Name Format Description
tpt.stepsize double step size of the test execution as specified in the platform
configuration
tpt.timeout double time out of the test execution as specified in the platform
configuration
15.10.4 MATLAB platform configuration variables
Name Format Description
tpt.matlab.modelname text Name of the test frame model to be executed
tpt.matlab.modelfile file File name of the test frame model file that is responsible
for execution
tpt.matlab.modelfile.dir dir Directory where the model file (test frame model file) is
stored
tpt.matlab.version text Logical name of the MATLAB version
tpt.matlab.rootdir file Directory where MATLAB is installed
tpt.matlab.restartnow int This preference is 1 if MATLAB will be restarted
immediately. Otherwise the value is 0. MATLAB will be
restarted (value is 1) if and only if the parameter “Restart
MATLAB every X tests” is set and if the given number X of
tests has been reached.
tpt.matlab.paramstoworkspace text This variable will be substituted by a sequence of mstatements
that set all the test parameters of type
EXCHANGE defined in the TPT test case as MATLAB
workspace variables. In order to use this feature, just add
${tpt.matlab.paramstoworkspace} as a
statement into your run test script.
15.10.5 Backbone platform configuration variables
Note, that the following variables are only available together with the backbone integration
extension of TPT, which is not part of the regular TPT installation. The backbone platform allows
interaction with the Backbone simulation environment for SIL simulations. This platform has
been developed by DaimlerChrysler. For more information send an email to
tpt@piketec.com.
Name Format Description
tpt.backbone.rootdir dir root directory of the backbone installation (dir that contains
“dllkopp/bin/backbone.exe”)
tpt.backbone.config file the “bbc-file” which is the file that describes the modules to
be loaded by the backbone. See backbone documentation
about details. This file is configured in the backbone config
panel
tpt.backbone.workdir dir directory where the backbone will be started
15.10.6 Scenario specific variables
Name Format Description
tpt.scenario.name text Name of the currently executed scenario
tpt.scenario.groupname text Name of the group of the currently executed scenario
tpt.scenario.id int Unique ID of the currently executed scenario
tpt.scenario.dir dir Directory where data for the currently executed scenario is
been stored
tpt.scenario.islast int This preference is 1 if the current scenario is the last one that
is being executed using the current settings. The preference

TPT User's Guide Page 87
is 0 if another scenario will be executed immediately with
the same configuration settings.
tpt.scenario.tvmfile file The filename (complete absolute path) of the JVM file
corresponding to the currently running scenario
tpt.scenario.tptbinfile file The filename (complete absolute path) of the TPTBIN file
containing the results of the currently running scenario
tpt.scenario.measurementfile file The filename (complete absolute path) of a measurement
file (file containing the measurement values), if any. This
variable does not exist, if there is no measurement in this
context.
tpt.scenario.parafile file The filename (complete absolute path) of the parameter file

15.10.7 Overview
Data dir
Execution configuration MATLAB configuration Backbone configuration
Reference dir
Report templatre
Attribute values
Logfile
Startup dir
tpt.rootdir • • • • • • • • • • • • • • • • • •
tpt.tptfile • • • • • • • • • • • • • • • • • •
tpt.tptfile.dir • • • • • • • • • • • • • • • • • •
global variable settings • • • • • • • • • • • • • • • • • •
tpt-file specific variable settings • • • • • • • • • • • • • • • • • •
tpt.testdatadir • • • • • • • • • •
tpt.date • • • • • • • • • • •
tpt.time • • • • • • • • • • •
tpt.stepsize • • • • • • • • • • • • • •
tpt.timeout • • • • • • • • • • • • • •
platform specific user variables • • • • • • • • • • • • • •
tpt.matlab.rootdir • • • • • • • • • •
tpt.matlab.version • • • • • • • • • •
tpt.matlab.modelfile • • • • • • • • • •
tpt.matlab.modelfile.dir • • • • • • • • • •
tpt.matlab.modelname • • • • • • • • • •
tpt.matlab.restartnow •
tpt.backbone.rootdir • • •
tpt.backbone.config • • •
tpt.backbone.workdir • • •
tpt.scenario.name • •
tpt.scenario.groupname • •
tpt.scenario.id • •
tpt.scenario.dir • •
tpt.scenario.islast • •
tpt.scenario.tvmfile • •
tpt.scenario.tptbinfile • •
tpt.scenario.parafile • •
Startup script
Original model
file
Original model
load script
Original model
path
Generate test
frame model file
Exec config test
frame model file
Exec config
model load
Exec config run
test script
Backbone dir
Backbone config
file
Backbone
working dir
Backbone
command

16 Index
add unambiguous variants ............................................ 32
additional parameters, specifying ................................... 7
assessment
engine ......................................................................... 6
Auto-completion ........................................................... 81
automaton fragments
export into an image file ........................................... 24
save ........................................................................... 24
TPT import ................................................................ 24
automatons
copy .......................................................................... 24
cut out selected automaton...................................... 23
debug ........................................................................ 73
delete ........................................................................ 23
export into an image file ........................................... 24
move ......................................................................... 23
parallel automatons .................................................. 22
view ........................................................................... 25
automatons, select
select individual ........................................................ 23
select multiple .......................................................... 23
breakpoint
find ............................................................................ 75
browser
scenario....................................................................... 8
teslet ........................................................................... 8
C-code testing ............................................................... 51
channel,assigning
local ........................................................................... 14
observation ............................................................... 13
stimulation ................................................................ 14
channel,declaration ....................................................... 10
change....................................................................... 12
create ........................................................................ 11
delete ........................................................................ 12
editor ........................................................................ 10
clipboard
copy automaton elements as an image .................... 24
insert automaton elements ...................................... 24
column
first ........................................................................... 84
fourth ........................................................................ 84
second ...................................................................... 84
third .......................................................................... 84
constant,declaration ..................................................... 10
change ...................................................................... 12
create........................................................................ 11
delete........................................................................ 12
editor ........................................................................ 10
converter data ................................................................ 6
create elements
final node elements .................................................. 17
initial node elemnts .................................................. 16
state elements .......................................................... 17
data converter ................................................................ 6
debug
basic modules ........................................................... 73
execute a test ........................................................... 76
plug-in-features ........................................................ 74
definition
parameter ................................................................. 32
scenarios ................................................................... 32
direct-definition,testlet ................................................. 26
signals ....................................................................... 28
editor
template ............................................................. 62, 64
environment
MATLAB/Simulink ..................................................... 41
variables ............................................................. 51, 85
variables ................................................................... 44
equation, testlet
change order ............................................................ 27
define........................................................................ 27
Error message
Compilation on the fly .............................................. 25
EXE Platform ................................................................. 49

Page 90 TPT User’s Guide
executing TPT
assessment.................................................................. 6
command line ............................................................. 6
executing TPT .................................................................. 5
execution
configuration variables ............................................. 85
EXE-Platform
platform configuration .............................................. 51
test C Source-code .................................................... 51
TPT-VM-API ............................................................... 50
Exit TPT ............................................................................ 9
export
automatons and automaton fragments .................... 24
function
history ....................................................................... 81
replace ...................................................................... 80
search........................................................................ 80
function wizard
access ........................................................................ 69
asymptote function ................................................... 71
constant .................................................................... 70
individual functions ................................................... 70
motivation................................................................. 69
periodic function ....................................................... 71
ramp function ........................................................... 70
target ........................................................................ 69
import
automaton fragments ............................................... 24
interface .............................................................. 45, 82
interface
import ....................................................................... 45
intermission points ........................................................ 57
junction, create ............................................................. 22
log server ......................................................................... 6
MATLAB
close model and MATLAB ......................................... 48
Console ............................................................... 42, 44
environment ............................................................. 41
exchange parameter ................................................. 33
Log-file ...................................................................... 42
mat file ...................................................................... 28
Model load script ...................................................... 43
open Simulink testframe model ................................ 48
platform .................................................................... 41
platform configuration variables .............................. 86
Ports .......................................................................... 42
RMI communication .................................................. 42
start procedure ......................................................... 47
Startup-dir ................................................................. 42
test execution procedure .......................................... 47
Test run script ........................................................... 44
Object overview ............................................................ 84
options
generator .................................................................... 7
log server .................................................................... 6
parameter
array .......................................................................... 33
definition................................................................... 32
exchange with MATLAB ............................................ 33
scalar ......................................................................... 33
parameter,declaration .................................................. 10
change....................................................................... 12
create ........................................................................ 11
delete ........................................................................ 12
editor ........................................................................ 10
path variants
select ........................................................................ 30
pauses ........................................................................... 57
platform ........................................................................ 41
EXE ............................................................................ 49
EXE-executable ......................................................... 49
select ........................................................................ 41
standalone ................................................................ 54
plug-in features
debug ........................................................................ 74
plug-ins ........................................................................... 6
replace .......................................................................... 80
report
editor .......................................................................... 7
generator .................................................................... 7
report template editor .................................................. 64
Restore .......................................................................... 84
scenario
browser ...................................................................... 8
variables ................................................................... 86
scenario groups
comment .................................................................. 38
create........................................................................ 36
delete........................................................................ 37
nameing .................................................................... 37
rename ..................................................................... 37
scenarios ....................................................................... 29
comment .............................................................. 8, 38
creat scenarions and groups ..................................... 36
delete scenarios and scenario groups ...................... 37
direct definition ........................................................ 32
naming ...................................................................... 37
organisation .............................................................. 35
rename ..................................................................... 37
time partition............................................................ 29
search ............................................................................ 80
select automatons
select individual ........................................................ 23
select multiple .......................................................... 23
selection
clear .......................................................................... 23
server
loging ........................................................................ 83
Simulink
environment ............................................................. 41
platform .................................................................... 41
Spreading of combinations ........................................... 84
Spreading of variants .................................................... 84
starting TPT ..................................................................... 5
start-up procedure, problem .......................................... 7
state variants
select ........................................................................ 30
states, rename .............................................................. 18
Statistics ........................................................................ 83
template
create........................................................................ 64
editor .................................................................. 62, 64
elements ................................................................... 66
load ........................................................................... 66
save ........................................................................... 66
test
execution .................................................................. 55
test analysis................................................................... 59
test data viewer ............................................................ 59
modes ....................................................................... 61

TPT User's Guide Page 91
shortcuts ................................................................... 61
test frame
generate .................................................................... 46
test models,create, save and load ................................... 9
test sets
selection .................................................................... 39
testlet
browser ....................................................................... 8
content delete .......................................................... 35
create ........................................................................ 35
deletion ..................................................................... 35
embedded ................................................................. 18
graphical modelling ................................................... 15
organisation .............................................................. 35
rename ...................................................................... 18
rename ...................................................................... 36
testlet, signature ........................................................... 13
textual notes
create ........................................................................ 22
transition specifications
select ........................................................................ 31
transitions
add , move and remove contorl of points .......... 19, 20
create........................................................................ 19
establish.................................................................... 19
name ......................................................................... 20
reconnect.................................................................. 21
rename ..................................................................... 20
user guide ....................................................................... 5
variables
scenario .................................................................... 86
window
breakpoints-overwiew .............................................. 79
channel watch .......................................................... 79
control-debug-session .............................................. 78
documentation ........................................................... 8
editor .......................................................................... 8
main ............................................................................ 7
menu,tool bar ............................................................. 9