TPT is a test tool for testing embedded systems, especially the testing of control systems. TPT supports all important fields of the test process which are in detail the management of tests, test modelling, test execution, test assessment, and test documentation.

Reactive Tests: TPT supports reactive tests, that is to say tests, which can react on the system’s behaviour during the test execution. Particularly when testing control systems, this possibility is essential because test cases mostly show a reactive nature in these fields.

Support of Tests with Continuous Signals: In the field of control engineering the in- and output variables often are continuous signals. On the market, TPT is the only systematic test tool for reactive tests of embedded systems supporting the easy modelling of test cases with continuous signals.

Automated Tests: Most of the steps of the testing process are being automated by TPT. This considerably shortens the expenditure of time for the test execution, test assessment, test documentation, and the test management. Especially at the development processes for embedded systems which often proceed strongly iterative, the automation allows efficient test repetitions and so an optimal integration of test activities into the development cycles.

Consistency: TPT allows the repetition of tests in different »in- the-Loop«-environments without modifying the test cases for the exchange between Model-in-the-Loop (MiL), Software-in-the-Loop (SiL) and Hardware-in- the-Loop (HiL). This is possible because TPT uses both a platform independent test description language and a platform independent test machine which can be integrated in almost any test environments.

Many Platforms: Simple integration in all test-platforms (e.g. MATLAB/Simulink, LabVIEW, C-Code)

Systematic Testing: A systematic and structured choice and modelling of the test cases is of particular importance, because testing always is an empiric operation that can not prove the system quality entirely. In TPT test cases are not being looked at isolated of each other. Instead, all test cases are being created in a common model with the objective of working out common and different characteristics in order to get an overview about which aspects have been tested and which might have been neglected.