Testing AUTOSAR software components is easy and automated with TPT.
TPT offers a solution for atomic AUTOSAR software components (SWCs) as well as for compositions of several SWCs or for virtual ECUs.
For given SWCs and their associated ARXML files, TPT automatically generates a test harness for functional tests. This test harness integrates a test RTE which is generated by TPT for one or more SWCs.
Important interfaces such as client/server ports, sender/receiver ports, per-instance memory (PIM), inter-runnable variables (IRV), mode declaration groups, exclusive areas and calibration parameter ports are supported.
Alternatively, FUSION nodes can be generated from SWCs in a very similar way as a test environment for co-simulation of multiple SWCs or for interaction with other software or dynamic models.
If your AUTOSAR software components have been developed with Simulink or TargetLink models you can easily test and compare the behavior of the generated SWC code with the behavior of the original models with TPT. Easily transfer functional tests and test assessments from MiL to the AUTOSAR test environment and compare the results by means of fault-tolerant back-to-back testing.
Processor-in-the-Loop testing (PiL) refers to the testing and validation of embedded software on the processor that will later be used in the Electronic Control Unit (ECU).
What is Software-in-the-Loop testing? How do you do SiL testing? Here, we give a concise answer to those questions and highlight its role in model-based-development.
If you are just getting started with TPT this tutorial is for you. In a few simple clicks you can set up your first test case and and start testing.
