How do you write automated tests that support change in the application under test, instead of tests that require every bit as much maintenance as the application itself?
How can I write tests on top of a legacy application that isn’t designed for automated testing?
How many tests do I need, and should they be unit tests, integration tests, end-to-end tests, or some combination of them all?
How do I write automated tests without losing the forest for the trees so that I can test that my application behaves correctly rather than testing that my application behaves as it currently does?
This month’s topic was all about testing with abstraction layers, a technique that will help you navigate all of the above questions and more so you can write just the right amount of focused tests, at the right level, to gain maximum value.