The software architecture described by AUTOSAR is a widely-used standard across the globe’s automotive software industry. Functional software is implemented in so-called AUTOSAR software components (SWCs).
Testing AUTOSAR’s SWCs can be done easily with TPT, and is easily automated. What’s more, you can test atomic SWCs, compositions of multiple SWCs and do virtual ECU testing with TPT.
Automatic generation of test harness & runtime environment (RTE)
TPT automatically generates the test harness for interfacing, which in turn serves as a test runtime environment (RTE), also generated by TPT.
The interface with TPT is specified using ARXML files (special AUTOSAR XML files). Multiple interfaces are supported, such as:
- Client/ server ports
- Sender/ receiver ports
- Per-instance memory (PIM)
- Interrunnable variables (IRV)
- Mode declaration groups
- Exclusive areas
- Calibration parameter ports
Testing SWCs works like “Plug&Play
Thanks to the seamless integration of components and testing tool, testing AUTOSAR SWCs with TPT is straightforward.
The integration is done via the generated RTE. This is done either for closed systems or by way of our co-simulation platform (FUSION) for simulating virtual ECUs.
In other words, you can test AUTOSAR SWCs directly with TPT or via plant models for complex and dynamic systems. SWC can also be tested individually, compositions thereof, or integrations of plant models of complex and dynamic systems. Software testing with TPT is virtually plug and play testing (or, as we like to call it: run, test, drive).
Standard AUTOSAR & AUTOSAR Adaptive
PikeTec is an Associate Partner of AUTOSAR. For testing according to the AUTOSAR standard, we offer special solutions for AUTOSAR SWCs for the latest versions of AUTOSAR 3, AUTOSAR 4 and AUTOSAR Adaptive.
Feel free to browse through our Glossary of Test Terms in case you are looking for terminological explanations.