Modeling tests in TPT
In TPT, tests are described graphically with hybrid automatons and with test steps. You can use external measurement data in test step lists or let TPT generate test cases based on those measurement data. You can use conditions as well as functions in the test model. The test model itself can be hierarchically or in parallel, or uses both approaches.
You have the freedom to create an unlimited number of variants of the states and transitions.
The appropriate state variants, transition variants, and the paths of the automaton that should be taken are selected in the test cases. Since tests in TPT are reactive, you can define state-based decisions as well as state-based transitions.
TPT assists you with numerous features to generate meaningful test data, for example TASMO for the test data generation from Simulink models.
To model tests graphically, extended state-transition-diagrams, called TPT-automatons, are used. A TPT-automaton specifies graphically which states and phases are part of the test, how much time a state consumes, and under which conditions states may change.
The different combinations of state sequences, variants of states, and transition conditions constitute individual test cases. These individual test cases are not viewed independently but they are presented in a joint 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 yet.
Test Step Lists
Test steps are made up of sequences of commands. These sequences are processed successively or in parallel.
You can model test steps using hierarchies, conditional statements, parallel sequences, reactive behavior, or loops.
Signals are defined by assigning values, time-dependent synthetic functions, or by imported measurement data.
You can embed or link measurement data from various file formats like *.csv, *.dat, *.mat, *.mf4, *.mdf, *.tptbin or *.xls in test step lists.