Chapter 11. Automated Integration Testing
Automated integration testing is a pig, but it's an important pig. And it's important for precisely the reasons it's so difficult.
The wider the scope of your automated test, the more problems you'll encounter; but these are also "real-world" problems that will be faced by your code, both during development and when it's released. So an integration test that breaks—and they will break frequently, e.g., when a dependent system has changed unexpectedly—isn't just a drag, it's providing an early warning that the system is about to break "for real." Think of an integration test as your network canary.
Integration ...
Get Design Driven Testing: Test Smarter, Not Harder 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.
