Legacy code is a real problem with C++ applications. With so many developers working on the same codebase over time – decades even -- your code gets complicated and full of dependencies.
Unit testing is often the best solution to ensure that your legacy code does what it’s supposed to do. But sometimes unit testing C++ legacy code can be problematic.
Learn how to:
• deal with global C functions
• deal with private calls to functions that you want to avoid
• deal with your code creating objects that you want to ignore
• test when there is no external state to check
• simulate values that are returned by reference
Loading more stuff…
Hmm…it looks like things are taking a while to load. Try again?