Reviewing junit.org's articles this past weekend, I was intrigued by the notion of using JUnit to define contract behavior. I think the specific mechanics described by Anders Eliasson in Implement Design by Contract for Java using Dynamic Proxies goes too far to be practical for rapid application development (or even "somewhat timely application development"). But I like the idea of using tests to define contracts.
Testing Interface Compliance with Abstract Test by Eric George describes something a little closer to what I'd like: automated testing that's part of the build cycle to be used as a compatibility/compliance test.
Something's percolatin' in my head along this axis...
12:37:04 PM 
|
