Teardown

Building multithreaded code is perhaps the most difficult task in software development. Few of us regularly write code that must support concurrency, which makes it that much harder. Using TDD, your approach to multithreaded code moves in the direction of scientific method and away from mystic art. Instead of hoping that your reasoning around concurrent execution is correct and instead of throwing locks and synchronization at any problems, you use TDD as a tool to validate or disprove your hypotheses about where the concurrency issues truly lie.

We’ve covered all the major topics in test-driven development. You’ve learned how to test-drive, you’ve learned how to test after when necessary, and you’ve learned how to tackle the specific problem of multithreading. Next up, you’ll delve into a number of odds-and-ends topics about TDD.