Motorola

In addition to writing the report on training as required by the module, I mainly handled two tasks. Using the CETK, which I wrote few months back, I was asked to conduct functionality and unit testing on the firmware code being written. As the current power micro firmware which is in assembly language is non-maintainable, it was decided to write it again in C language more efficiently and cleverly. Thus it was required to test the conformance with the existing specification, functionalities and API. CETK was used to run automated unit tests on the code, where initially four of them failed. Subsequently the code was modified in steps, and finally except for the yet to be implemented EEPROM write function, all other tests passed.

In CETK, as in any other unit tests, we prepare test cases and write functions to utilize the existing function calls and APIs, often repeatedly, and it is uncommon to go to the abusing extent to verify the robustness of the code.