“Testing leads to failure, and failure leads to understanding”. This statement also holds true in the context of Software Testing of the Embedded Systems.
Based on the SDLC (software development lifecycle), various software testing methods are deployed, in order to identify the failures and proactively correct them.
One such important testing method is the Unit Testing of embedded system software.
Unit testing is designed to test the smallest testable part of the software, called as Unit. The purpose behind unit testing is to verify that each unit is behaving in the intended manner.
This testing requires additional due diligence, when it is applied for automotive software, intended to achieve ISO 26262 compliance.
For Functional Safety projects, the testing guidelines prescribed by the ISO 26262 standard, will define your unit testing strategy. While they are similar to regular Unit Testing methodology, the guidelines are focused on functional safety of the software.
Through our latest video on ISO 26262 series, we will throw light on unit testing aspects of functional safety.
Highlights of this ISO 26262 Compliant Unit Testing Video:
- Understanding Unit Testing w.r.t Functional Safety
- Unit Testing strategies as per ISO 26262 Part 6.9
- Methods, Test Cases, and Coverage as per Table 10 of ISO 26262
- ISO 26262 Recommended tools and their role in Unit Testing
The intention of this video is to help you understand what happens when ISO 26262 meets software unit testing. You can also refer to our detailed blog on the similar topic here. /blog/embedded-blog/how-iso-26262-compliant-unit-testing-strategies-manifest-in-automotive-software-development
Our series of video on ISO 26262 and automotive functional safety will continue with more such informative videos. Stay tuned!
