Wait! Is this really already blog #50?

Let’s take a moment to recap. What have we written about over the last four years? If you’ve read all 49 of our blogs, well done! Of course, you have to find the time to read them and make sure you don’t get distracted. Are you afraid you might have missed...

The caveats of standard library qualification

The big advantage of the standard library is that most library functions are independent of the other functions in the library, both in their specification and implementation. This lowers software complexity and simplifies verification, thereby reducing qualification...

After compiler qualification comes the Application Hazard Scanner

Our Compiler Qualification Service is a fast and efficient way to get your compiler qualified. On completion, you receive a compiler qualification report compliant with the functional safety standard that you specify. Yet, no compiler is perfect. The report will...

Using libraries safely is your responsibility

Functional Safety standards require that the user of the library takes responsibility for the library, even if it comes from a third party. Library code becomes part of your safety-critical target device, so it has to be verified as fit for purpose. As the application...

Not all test suites are created equal

We are often asked what differentiates SuperTest from the GCC and LLVM test suites. If you are using the LLVM or GCC test suite, why would you use SuperTest as well? Apart from the obvious answer “more testing, preferably using tests with different origins, is...