Chapter 12. Interlude: Test-Driven Plug-In Development
When we began writing the code for this book, we did it in a classic exploratory style. We thought of some functionality we'd like to add. We browsed in Eclipse to get some ideas about how to implement it. We put some code together. We looked at the result of the new code in the run-time workspace. We repeated as necessary.
As we made progress, we quickly learned developing only in the exploratory style we were not able to write code without errors. Say we had added some functionality. Were we sure we hadn't broken something? We aggressively refactored our code to improve its structure. Were we sure we hadn't broken something? We wanted a way to regain confidence in our code.
The benefits we ...
Get Contributing to Eclipse: Principles, Patterns, and Plug-Ins 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.
