Unitizing Legacy and New Code for Unit Testing

All code is unit testable, regardless of its origin and current state. Although it may not appear so, there are techniques you can use to safely get any piece of code under automated unit tests. Michael Feathers shows the dependency breaking techniques he has used to safely de-couple legacy code for unit testing. He discusses not only the different challenges in Java, C#, C++, and C but also common heuristics you can use to bring your code under test. Learn about the value and power of deterministic change with fully automated unit tests. Identify internal and external dependencies in sections of code and establish ways to break these dependencies with or without refactoring tools.