Test modeling

In TPT, tests are described graphically with hybrid automatons, test steps, synthesized signals, and measurement data. An automaton can be modeled hierarchically or by using parallel processes, and by setting decisions and functions.

States of automatons and transitions can hold variants of themselves that represent different scenarios, similar to equivalence classes. Tests can behave reactive, so it’s possible to model controllers on your own or set decisions or transitions based on a specific state.


Graphical test modeling with automatons

To model tests graphically, extended state-transition-diagrams, called TPT-automatons, are used. These TPT-automatons specify graphically which states and phases are part of the test, how long the duration of the parts and phases is, and under which conditions states may change.

The different combinations of state sequences, variants of states, and transition conditions are regarded as individual test cases. In TPT these individual test cases aren't observed isolated from each other, but on the contrary they are presented in a single model, where similarities as well as differences between the test cases clearly stand out. Moreover, this way the tester gains a detailed overview of the aspects that were tested and those that weren't.


  • TPt test modeling: On a junction, it is determined during runtime which branch to take according to the transition conditions (t>23, t==23, t<23).
  • TPT test modeling as parallel automaton with active paths in black and inactive paths grey.
  • Modeling test pases with TPT.
  • You can set up variants of states and transitions. With these variants, you can effectively and easily create test case variations.

Automatons in TPT [16 MB]
Testlet, what's that? [9,4 MB]

Test Step Lists

Test steps can be built from sequences of commands. The test steps are successively activated period after period or run in parallel. It’s possible to model hierarchies, conditional statements, parallelisms, reactive behavior, or loops with test steps. Signals are defined by assigning simple values, time-dependent synthetic functions, or measurement data that was imported into TPT.


  • From TPT9 on, it will be possible to run test steps simultaneously.This feature complies with the parallel automatons in the graphical test modeling.
  • You can set up direct definitions as a single-line mathematical formula. Or you use the convenient Direct Definition Function Wizard.
  • Inside a test step list, you can change parameter values, as well as reset single parameters or all parameters to their default value.
  • You use the Compare Step to check if a condition is true. Here: when the light_switch is set to "on", check if the headlight is "on" too.
  • You can deactivate test steps in a test step list to exclude them from the test execution. You can, of course, activate them again easily.
  • You are free to insert comments in the test step list.
  • The behavior of signals can be controlled by using If and Else steps. Here: if "a" is greater than 3.5, ramp the channel "foo" every two seconds two units up until 6 is reached. Else, ramp "bar" to 5.
  • You can influence the duration of a state by linking it to the fulfilling of a condition (Wait...). Here: wait until the length of  the embedded signal is reached, then terminate this step.
  • Using While steps, you can execute test steps in the loop, thus several times in succession.
  • You can nest While Steps inside a test step list.

Import of a single measurement file

It’s possible to import measurement data from various file formats like *.csv, *.dat, *.mat, *.mf4, *.mdf, *.tptbin or *.xls into TPT and embed it in test steps. Afterwards the data can be edited. Alternatively to embedding measurement data, the data can be linked to.


  • You can use a embedded measurement file as a normal test step. A signal preview is also possible.
  • From a single measurement file, you can embed several signals (channels and parameters) in TPT at the same time.
  • To take a closer look at the embedded signals, you can use the zoom function inside the signal preview.

Test case generation from measurement data

With huge amount of data, an easy to configure batch-import is available.

For each measurement file a test case is automatically generated. The signals of the measurement file can be chosen and mapped to already in TPT existing signals. Measurement data can be imported to use them as input signals for the stimulation of the system, or as output signals to use them as reference data.


Copyright © www.piketec.com    All rights reserved

Follow us