If your aim is to achieve the highest product quality in the development of embedded software, then you're likely familiar with the Automotive SPICE (ASPICE) process maturity model.

TPT ASPICE Process Maturity Model

ASPICE has become established as a process framework for suppliers and OEMs involved in the development of electronics and software-based systems. With our test automation tool TPT, you can effortlessly meet all process requirements for dynamic testing. Thanks to its intuitive user interface and extensively tested basic functionalities, you can achieve maximum efficiency in testing.

For all Automotive SPICE processes, you can create test cases as open-loop, closed-loop, and reactive using tables, step lists, and graphical test design. For an efficient approach, we recommend utilizing references for recurring implementations, separating test data and expected values, using parameter multi-execution, and automatic test case generation. 

Software Unit Verification

SWE.4 demands the verification of unit specifications. Testing and verifying at the unit level entails scrutinizing the smallest executable and testable software components. These could be individual files, functions, libraries, or generically designated elements in software design.

Unit Testing with TPT

With TPT, all units can be tested, whether as subsystems in a model (Model-in-the-Loop), as code (C-code testing), as components (AUTOSAR), or as Black-Box, Grey-Box, or White-Box. You can conduct unit test runs in the modeling environment, on the host, or in the target environment, and also compare different executions through back-to-back tests.

The functionality of TPT ensures a test process compatible with ASPICE. All requirements regarding dynamic testing, aligned with ASPICE Best Practices (BP) for unit verification, are met – including traceability between requirements from detailed design to test cases.


Software Integration and Integration Test

Do individual software components interact as planned? Are interfaces correctly connected and compatible? In SWE.5, multi-stage software integration tests based on the Software Architectural Design are conducted.

The focus is therefore on the interaction and combination of the assembled units into a larger, self-contained software entity.

In our experience, this testing stage uncovers most errors. A multi-stage integration approach is considered the most promising solution for sustainably managing software complexity.

Software Integration Testing with TPT

With TPT, you have a complete toolbox for all challenges related to software integration testing. Complicated signal flows can be modeled in real-time, evaluations can be conducted using equivalence classes, and interface tests can be generated. Execution can take place on a local computer, on the target control unit, in a CI environment, and in the cloud. For all software integration tests, all code coverage metrics are available in all execution environments.

TPT also enables time-saving and consistent testing at this point through Assesslets and a well-structured test design.

Software Qualification Test

Testing the complete software concludes the software testing activities according to Automotive SPICE with SWE.6. The goal is to demonstrate the fulfillment of all software requirements. In many cases, the test execution takes place directly on the target hardware. This allows you to verify that the software runs correctly on the hardware.

Software Qualification Testing with TPT

TPT can represent software qualification testing in two ways:

  • Using an emulator to abstract hardware-dependent interfaces, presented in the form of a virtual ECU
  • Connecting the combination of hardware and software to TPT.

For hardware integration, TPT offers many integrations with commonly used automotive hardware test bench solutions and additionally supports the open ASAM XIL standard. For simpler control units with pure CAN interfaces, control units can be connected and tested as so-called bench setups with a HW-CAN interface.

System Integration and Integration Test

After verifying that the software runs on the control unit, the control unit undergoes multi-stage integrations in the system context. An iterative-incremental integration approach is recommended. Hardware components are integrated with real sensors, actuators, and other control units to demonstrate functionality within the E/E architecture. Testing is predominantly conducted on test benches, using Hardware-in-the-Loop Testing.

Questions such as "Does the body controller function for controlling exterior lights also work with the current light sensor?" or "Are there any issues in bus communication?" are clarified at this testing stage.

System Integration Testing with TPT

With TPT, errors in the system context can be quickly identified. Test cases from previous testing stages can be reused, saving valuable time and resources. Complex hardware test benches are typically used at this stage, and TPT can communicate with all these test benches and automate your tests.

System Qualification Test

The highest level of assurance according to Automotive SPICE is the System Qualification Test. The fully integrated vehicle with all its software, control units, and sensors is ready and can now be tested. All customer functions and services must operate properly in conjunction.

System Qualification Testing with TPT

In addition to automated tests with TPT on the common HiL test benches, the Autotester from TPT provides significant added value by facilitating manual driving maneuvers. Driving maneuvers described in the Autotester help simplify the correct execution of even complex driving maneuvers. Monitoring of the execution correctness is continuously done by the Autotester, and the evaluation of driving maneuvers is fully automated. At any time, a driver can document anomalies during execution by making voice recordings. The trace generated and prepared by the Autotester is supplemented with the voice message from the driver. Later analysis is significantly simplified with these annotations.

Support and Training


Explore the Synopsys Support Community! Login is required.


Erase boundaries and connect with the global community.

Connect with the Synopsys TPT Team