loader image

Test Solutions for Simulink Models & Production Code

Virtual Validation for ADAS/AD

How can I create the needed millions of scenarios?

How can I avoid the test explosion problem?

How can I find out if my tests are passed or failed?

3 Reasons to Consider Using a Floating-Point Model to Generate Fixed-Point Code

Despite the availability of fast processors with dedicated floating-point support, we still see many projects generating fixed-point code from Simulink. The reason for this is not only the resource usage, but also the more transparent and predictable mathematical behavior. You can read more about this in our previous articles “What you should know about fixed-point” […]

What You Should Know About Fixed-Point Code

Fixed-point Code - What you should know - Blog Article

Vocabulary: Floating-point code? – Fixed-point code? – Scaling? – Resolution? – LSB? Basically, we can distinguish between two kinds of datatypes in embedded code: Floating-point and Integer. An integer variable basically represents whole numbers and the value range is limited by the number of bits. For example, an (unsigned) 8bit Integer can represent 2^8=256 different values, by default […]

When and how to generate test cases automatically

The automatic test case generation has always been a controversial topic. While some people dream about stopping any manual test activities others say that test generation is not allowed. But who is right? Test Goals for automatic test case generation Let’s have a quick look at the possible test goals for which we can generate […]

Modular Model-based Software Architecture for Efficient Unit and Integration Test

Component-based architecture in Simulink

Model-based design (MBD) is well established in automotive to develop embedded software but with the growing size and complexity of software, handling big sized model is often a challenge. MBD enables to easily craft a software application and from one step to another refine it, test it and generate the production code. However, it’s risky to start […]

Should I test the Model or the Code?

Model-based software development (MBD) with tools like Simulink and TargetLink in the automotive industry has grown over the past years and is a well-established development methodology today. Despite all the advantages, it can’t be denied that MBD introduces one additional step in the development process. In addition to the production C code there is also […]

What you should know about code coverage

Each time we talk about testing, we also talk about code coverage. But why is it important to keep an eye on code coverage and what are possible code coverage goals? What is code coverage? Code coverage is the sum of all coverage goals that are covered by a set of test cases. Coverage goals […]

What you should know about floating-point

Floating-point code becomes more and more common in today’s automotive industry. Since development is often done model-based using tools such as Simulink and dSPACE TargetLink, the model serves as an additional abstraction layer and therefore is an additional stage in the development and testing process. In comparison to fixed-point, floating-point comes up with several advantages. […]

How to efficiently handle external variables in a TargetLink Unit Test


In the last decades, Model-based development (MBD) has considerably improved the development of embedded software in the automotive industry. Although the MBD methodology increases the efficiency of the development process, there are some technical challenges which function developers often experience. One example is the handling of external variables during software unit test. In this blog […]