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.
Imported measurement data
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.
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.