Hello.
First thanks for your articles on this subject. I’m an embedded developer recently found that I’m missing unit testing to make better code without bugs or the painful task of debug code.
I found your articles, and they are well explained, with good examples, and I was convinced.
However, I would like to make a small question. I found that your way of organize files was easy to understand and an excelent approach. However, on the cpputest site they point to a repo (GitHub - jwgrenning/cpputest-starter-project: gcc cpputest starter project, with instructions to help get your legacy code into cpputest for the first time) that is from the author of the renamed book on this subject. I found that file organization a little more hard to understand, and it does not seem to make use of separate makefiles for different tests, as you do.
I know I’m starting this up, and I’m reading that book, so maybe I’ll understand more later, but can you tell what advantage that way of structure has? Or do you find your way better?
Sorry for the long post, and reactivation of this topic.
Thanks for all your help.