Course overview:

The Test-Driven Development process implies in its purest form: 1st, define what/how the feature shall be tested and its interface; 2nd, implement the test, 3rd, implement code forming the feature and make its test(s) to pass; finally, 4th, refactor the code in order to fit into an appropriate standard - i.e., an architecture. The driving force behind TDD is the Unit Test.

The principal goal of unit testing, in embedded systems, is to take the smallest piece of testable code in an application - e.g., a device driver. Then isolate it from the rest of the code, and determine whether it behaves as expected. Chiefly it is the outer observable behavior we are verifying. Each unit is tested separately before integrated into higher order modules. Unit testing has proven its worth in that a large percentage of defects are identified during its use. In addition, a Unit Testing…