Following up about some questions from my presentation at the tech forum on the TF-A unit testing framework.

In regards to the other tool that was investigated alongside CppUTest, it was Google Test. The main reason for choosing CppUTest was that it is easily portable to new platforms and has a small footprint despite its feature set. This could be very useful if we want to use it on hardware (not on the host machine) in the future, even if it only has a small amount of memory. Google test is very good for testing user space applications, but most of its features require pthread, file system, and other services of the operating system which we usually don't have in an embedded environment. So we chose CppUTest because it fits for both host and target based testing so we won’t end up using different frameworks in the same project. Something to note is that CppUTest has an option for running Google Test based test cases too, but the intention is to keep the framework clean by using only CppUTest.

Also c-picker can support parsing large data structures since the tool uses PyYAML for parsing the config files and clang for processing the source files.

Thanks,

Lauren