Teardown
Keeping your tests clean and direct will promote your regular use of them as documentation artifacts. The more you seek to actively read tests and to always reach for the tests first, the more likely you will invest the effort needed to sustain them long-term. Use the guidelines provided in this chapter to help you recognize and correct problems with your test design.
You’ve learned a considerable amount about TDD so far. Your production code is clean and well-tested, and your tests are clean and helpful. But what about all the code that you or your test-driving teammates didn’t produce? “It was like that when I got here!” You’ll next learn a few techniques for dealing with the challenge of legacy code.
Get Modern C++ Programming with Test-Driven Development now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
