C/C++ Code testing

TPT can be used to test C- and C++ code on a PC. The test environment that connect the C-code with TPT can be generated automatically. TPT support multidimensional arrays, maps, curves, and structured data types. Function calls and function stubs are also supported by TPT. The test environment can be compiled with tools like GCC, Visual Studio, BCC, or LLVM. During the test debugging is possible.


EXE - Platform

The C-function or C-module to be tested has a predefined signal and function interface. Inputs and outputs of the system under test (SUT), as well as parameters and functions will be linked to TPT corresponding to their values.
An executable program is generated that cyclically runs the SUT and the test driver of TPT. This program, that connects the test driver with the SUT, is predominantly generated automatically.

The compilation of the system is independent of TPT and conducted by the user. Code coverage can be measured and shown with tools like CTC++ or Gcov.


Using TPT to test C and C++ code on the executable test platform

EXE - Platform

.mp4 [18,3 MB]

FUSION - platform

The FUSION platform is a test environment that allows co-simulation. Individual executable components, so-called nodes, can be linked to the FUSION with help of a simple C-API. This way, FUSION nodes can easily exchange function calls.
There are a lot of standard nodes already available for the FUSION, for example C-code, CAN, INCA, PLS UDE, ASCET, Simulink, Sound Emitter and external I-O-cards


Co-Simulation with TPT and FUSION for functional software test.

FUSION - platform

.mp4 [28,6 MB]

Testing and verifying AUTOSAR components

In AUTOSAR, the AUTomotive Open System ARchitecture, control systems are developed standardized and independently of the hardware. The software is divided into individual software components (SW-C) that communicate with each other via defined interfaces called ports using a real-time environment (RTE).

The tests are modeled as usual in TPT. Test and verification of AUTOSAR software starts in the course of module testing inside known development environments such as MATLAB/Simulink, ASCET, or as handwritten C-code with TPT.

Atomic SW-Cs or compositions of multiple SW-Cs can be tested with TPT without further tools. Based on describing ARXML files, TPT connects to the AUTOSAR SW-Cs to be tested and generates an appropriate test frame. Client/Server ports, sender/receiver ports, Per-Instance-Memory (PIM), Inter-Runnable-Variables (IRV), Mode-Declaration-Goups, Exclusive Areas, and CalPrm ports are supported by TPT.


Testing AUTOSAR components with TPT

Copyright © www.piketec.com    All rights reserved

Follow us