Testing C/C++ code

You can test C/C++ code via the TPT-internal virtual machine or by using the TPT-internal co-simulation platform FUSION.
The test environment that connects the C-code with TPT can be generated automatically by TPT.

You can use multidimensional arrays, maps, curves, and structured data types in your test settings.
Function calls and function stubs are also supported by TPT.
You can even debug your C-code during testing.
Tools like GCC, Visual Studio, BCC, or LLVM can be used to compile the executable.

Testing C and C++ via TPT's virtual machine

Using the EXE platform, you can test C and C++ code. You only need to connect the input and output signals of the system under test (SUT), the parameters, and the functions with the variables you have specified in TPT. After that, you create the test frame / test driver with your prefered compiler (for example GCC, Visual Compiler). You can always manually adapt the test frame as well as the test driver. Code coverage can be measured and shown with tools like CTC++ or Gcov.

You can also use the C platform to test your C-code. The advantage is that you can manage your C-code files and functions, and trigger the code instrumentation and the compilation of the test frame directly in TPT.
This platform also allows you to generate automatically test data with "TASMO for C" by PikeTec.

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

Testing C-code in co-simulation

Instead of testing individual C-code modules, you can test an abitrary number of software modules
as closed system via the integration platform FUSION by PikeTec.

Via the FUSION platform you can connect software modules that practically need different execution environments.
The modules can exchange data during the test run.

The FUSION platform supports many test environments like
C-code, CAN, INCA, PLS UDE, ASCET, Simulink, and external I-O-cards.

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

Testing and verifying AUTOSAR components

With TPT, you can test atomic AUTOSAR software components or compositions of multiple AUTOSAR components without the need for further tools. TPT connects to the AUTOSAR software components to be tested and generates an appropriate test frame based on the content of the ARXML file.

Client/Server ports, sender/receiver ports, Per-Instance-Memory (PIM), Inter-Runnable-Variables (IRV),
Mode-Declaration-Groups, Exclusive Areas, and CalPrm ports are supported by TPT.

Test execution on AUTOSAR software components in TPT

Follow us