Model-in-Loop testing and its consecutive development phases, Software-in-Loop testing and Processor-in-Loop testing, are interdependent throughout the development process by (at least) one particular testing method: Back-to-Back testing. This testing method especially applies to model-based designs and autocode generation with Simulink and TargetLink.
Back-to-Back testing is an integral part of software development, particularly in software engineering, as it ensures the System under Test (SUT) functions in later development phases as it does in earlier phases. Specifically, Back-to-Back testing means comparing the test results of different test executions, such as MiL and SiL, for example. As long as both the test results of both executions are similar the test is passed.
Advantages and Limitations of Back-to-Back Testing
The most evident advantage of Back-to-Back testing is that you can verify whether your SUT functions the way you intended it to function, as you go through the development stages. When passing from testing MiL (e.g. Simulink models) to testing SiL, the fix-point scaling of signals, for example, is particularly error-prone.
Every signal/ value is compared individually. Moreover, a tolerance range can be set to increase robustness (time and value tolerances).
ISO 26262 requires Back-to-Back Testing
Not only is Back-to-Back testing a very useful testing method, it is also required by ISO 26262. TPT fully supports Back-to-Back testing in compliance with ISO 26262.
Feel free to browse through our Glossary of Test Terms in case you are looking for terminological explanations.