Modern C++ Programming with Test-Driven Development

11.1 Setup

You’ve learned the who, what, how, why, and when of TDD. If you continue to practice TDD regularly to the point where you’re convinced of its benefits, you’ll someday become ​ test-infected​ [30]—you’ll insist on using it as your primary programming tool. You’ll quickly realize, however, that not everyone feels that way. Even if you’re part of a team that’s supposed to be test-driving your code, you’ll find varying levels of adherence and support. You’ll also encounter resistance and apathy, often based on lack of information. And even if your team is able to surmount the initial hurdle of getting everyone on board, you’ll find it a challenge to keep things from degrading over time—much like your codebase. Sustaining TDD is not easy. ...