Testing and verifying in all development phases
With TPT, it is possible to test control systems of all levels, thus also safety-related systems,
in every phase of the development process. From simple module testing to complex system testing inside a vehicle,
you can do anything. TPT provides unique ways to model tests intuitively and flexible.
Via interfaces, TPT can be connected to a lot of standard development tools.
Supported test environments
The test execution is based on a virtual machine (TPT-VM). This virtual machine is the same for all test environments and is integrated by means of appropriate adapters. This has the advantage that you can perform TPT tests in different “in-the-loop”-environments without the need to alter the test cases for model-in-the-loop (MIL),
software-in-the-loop (SIL), and hardware-in-the-loop (HIL).
Tests modeled with TPT are reactive and can react on the system's behavior during the test execution.
When required, they are also real-time capable.
MATLAB/Simulink and TargetLink
- Unit tests and integration
tests of Simulink models
- Unit tests and integration tests of TargetLink code in SiL and PiL
- Automatic generation
of test environments
- Automatic generation of meaningful test cases
- Unit tests and integration
of C-code on the PC
- Co-simulation with further software
- Code coverage analysis
- Automatic test case generation
Testing of physical and implemented models as C-code or with automatic generation of test environments in ASCET.
- Universal Debug Engine by PLS
- Simulink by The MathWorks
- TargetLink by dSPACE
- On a processor
Tests on hardware-in-the-loop (HIL) test benches like
- dSPACE HIL
- ETAS LABCAR
- Simulink Realtime
- NI VeriStand
- Concurrent iHawk HIL
- Customized HIL systems
CAN and LIN
- Test execution via
CAN and LIN busses
- Mapping of TPT-signals
to CAN messages
- Measurement and usage
of application tools
- Test bench automation
- Tests in vehicle
INCA and CANape
Automatic application and measurement via application tools with or without MCD-3.
- Automatic testing of
- Automatic access to CANoe
signals and system variables
Co-simulation of different environments, for example
- External I/O-cards
- Environmental models
- System models
- Functional tests of individual AUTOSAR software components
- Function tests of software component composites
and their runnables
- Automatic generation of test environments including communication between the ports
- Execution of tests inside a vehicle
- Automatic driving instructions
- Automatic assessment
Modeling test cases
With TPT, you can systematically create tests by using so-called automatons, test step lists, synthesized signals, and measurement data. TPT can generate tests automatically. Tests built with TPT are reactive, thus the tests can react on the system’s behavior during the test run.
Tests from equivalence classes
TPT can automatically generate test cases based on equivalence classes that were specified by you.
Tests from measurement data
TPT can automatically generate test cases form imported test data. The following test data formats are supported by TPT: *.csv, *.dat, *.mat, *.mf4, *.mdf, *.tptbin, and *.xls.
TASMO is a feature by PikeTec. TASMO can automatically generate test cases from Simulink models and from TargetLink code.
The Dashboard is a feature by PikeTec. The Dashboard let's you easily configure a virtual interfaces for manual testing. TPT can also record your interactions with the Dashboard and automatically generate test cases from these recordings.
Combination of variants
A TPT-automaton consists of states, paths, and transitions. The states, the paths, and transition conditions can be varied. TPT can automatically generate test cases from those variations
Assessing test results with assessment rules
TPT helps you in specifying rules for assessing test results. You can either use a mask or write more complex assessment rules in a TPT-specific script. Thanks to the auto-completion and the extensive help in TPT, both approaches are easy to manage. Finally, a detailed and significant report is created.
Linking requirements to test cases
Coverage analysis of test cases in TPT can be done by linking test cases with requirements. Tests and requirements can be exchanged with Requirements Management Tools. With the test evaluation, you can automatically check and document in TPT if the requirements are fulfilled or not.
Testing safety-related systems
Safety-related systems that have to comply with conditions for example according to ISO 26262, IEC 61508, DO-178C, or EN 50128 can be tested rule-consistent with TPT. PikeTec offers qualifications of TPT as testing tool for your development project. TPT supports requirements based testing, interface testing, fault injection tests, threshold tests, back-to-back tests, equivalence class tests, coverage analysis, and much more.
Using the Jenkins plugin by PikeTec, you can automatically run test cases created with TPT on a Jenkins continuous integration server.
Versions of TPT project can be managed with Subversion (SVN)
Java RMI-API for TPT
With a Java-API for TPT, most functions can be controlled and invoked remotely.
With TPT, test management for TPT projects is possible. Additionally TPT provides interfaces for example to TestLink, TestRail by Gurock Software or IBM's Application Lifecycle Management (ALM).
and much more