February 22nd, 10:00 CET (Berlin) / 04:00 EST (Detroit) / 14:30 IST (Bangalore) / 17:00 CST (Beijing)
February 22nd, 15:00 CET (Berlin) / 09:00 EST (Detroit) / 19:30 IST (Bangalore) / 22:00 CST (Beijing)
Even in domains like embedded software development for automotive, where we see a lot of model-based software development (MBD), different reasons may lead to projects being developed using handwritten c-code instead of applying a model-based approach.
Compared to MBD, handwritten code has a very low degree of abstraction. Testers need to figure out which functions to test and which variables they can access in a bunch of source files. Trying to isolate a function for unit testing proves even harder when it has a lot of dependencies.
In this context, we identify three main challenges:
Stubbing: The recurrent need to create stub code for external variables and functions
Architecture definition: The extraction of an architecture view of the test interfaces of each function
Test Harness: The creation of the test harness to write, execute and evaluate test cases
In this webinar, you will learn what you can do to address these challenges and how to ensure testability of your code.