Overview
The principal goal of unit testing is to take the tiniest piece of testable software in an application, isolate it from the rest of the code, and determine whether it behaves as expected – primarily: The outer observable behavior. Each unit is tested separately before integrated into higher order modules. Unit testing has evidenced its worth in that a large percentage of defects are identified during its use.
The Test Driven Development process implies in in purest form: 1st, define what/how the feature shall be tested; 2nd, implement code forming the feature and make its test(s) to pass; finally, 3rd, refactor the code in order to fit into an appropriate standard - i.e., an architecture. The driving force to behind TDD is the Unit Test.
Goal/Benefits
This twofold one day seminar – partitioned into an introductory part, and an advanced part - provides the participant with a number of concepts around TDD in terms of unit testing:
- Test-Driven Development – TDD
- Decoupling
- Software Architecture with Testability in Mind
- Embedded TDD Strategies
- DRY: Don’t Repeat Yourself!
- Legacy Code Testing
- Mocking
- Refactoring
Audience/Participants
This training is aimed for embedded system C programmers dealing with development of new features, as well as maintenance of existing legacy systems.