Testing and verifying ASCET models with TPT
ASCET by ETAS is a tool for model-based development and automatic code generation of control unit software in the automotive sector. The testing tool TPT supports the testing and verification of ASCET models. That is, ASCET models can easily be tested with TPT as physical or implementation model.
Compatible since ASCET 6.x
TPT is compatible with all versions of ASCET since ASCET6.x.
Test and verification of physical Model-in-the-Loop (MiL) and quantized implemented Software-in-the-Loop (SiL) is supported by TPT. You can also test individual modules or whole module groups in the form of an integration test.
Workflow of testing ASCET models
In ASCET, projects are developed with assigned modules, tasks, and processes.
The selection of the ASCET project to be tested (SuT) from the database or workspace is done via a special browser in TPT. It’s possible to test single modules or a complete module group (integration test) from a project.
The analysis of the interfaces of the system to be tested is based on A2L/DCM information from the ASCET project. Default values are imported from DCM files to be used for the default implementation configuration.
The assignment of interface values as inputs or outputs of the model and the local measurement values are determined through an analysis of the model. The test environment is automatically generated as a new ASCET project in TPT, consisting of the original model, the TPT test driver, and the associated tasks.
Besides functional requirements-based testing, TPT supports regression/back-to-back tests. Using TPT assesslets, the results of the test run can be evaluated.