Test-driven development can help to build software better and faster. It offers more than just simple validation of correctness; it can also drive the design of a program. In object-oriented programming, good use of encapsulation can make observing and testing some design features difficult. Further, the developer has to define classes and methods before compiling tests that use those classes and methods. Using the Java Management Extensions -- JMX -- to observe internal state provides an elegant alternative to reflection and compiler hacks. As a byproduct it provides a JMX interface for the completed system. This talk will cover how to benefit from unit testing with JMX, and the code and overhead required to use the technique.
Slides of this session are available as a PDF file [2].
You can download the MP3 [3] of this podcast episode directly, or copy and paste the java.net Community Corner mini-talks feed [4] into a podcast client like Juice or iTunes. You can also subscribe via the iTunes Store [5].
Links:
[1] http://www.java.net/author/david-walend
[2] https://java-net.dev.java.net/files/documents/29/95974/JMXforTestDrivenDevelopment.pdf
[3] http://download.java.net/general/podcasts/j1-2k8-mtW07.mp3
[4] http://feeds.feedburner.com/javanetJavaOnePodcasts
[5] http://www.itunes.com/podcast?id=153368676