Legacy Code Workshop
Our company has two main product lines, one based on C and one base on C++, thus we spent one day looking at the unit testing of legacy C code and one day working on the legacy C++ code. As a developer who works primarily on the C++ project I was not that interested in the C side of things although there was some useful information there. I would have been happier getting more involved in the C++ side of things but I also understand the need to implement TDD on the C side too.
How to improve:
A lot of time was spent dealing with external interfaces and dependencies from the legacy code that had to be fakes, mocked, etc. This process is necessary but takes up a lot of the class time. It would be more useful if a lot of this could be handled before the class starts so that we can see how to to begin testing the legacy code after getting it to compile and link, however, I understand that this is not a easy thing to do.