Tonight, I enjoyed a nice success. Specifically, I enjoyed the kind of success that I’ve found tends invariably to arise from using TDD — I wired some things together and discovered that everything just worked (well, at least my java code did – I did have a slight oops with javascript typos, but that’s to…
In this post, I’d like to point out something I learned while working following yesterday’s post. In my haste to find the JUnit equivalent of MS Moles, I didn’t stop to think about what I was doing. So, as I expanded on yesterday’s effort, I realized that my mocking of Runtime.getRuntime() didn’t seem to be…
Today, I’m continuing my series on unit testsing with JUnit with a target audience of C# developers. Goals These are today’s goals that I’m going to document: See about an NCrunch-equivalent, continuous testing tool for Eclipse and Java Testing the various complexities of the @PathVariable annotations Use mockito to perform a callback Mocking something that’s…
The Unit Test Value Proposition I gave a presentation yesterday on integrating unit tests into a build. (If anyone is interested in seeing it, feel free to leave a comment, and I’ll post relevant slides to slideshare or perhaps make the power point available for download). This covered the nuts and bolts of how I…
This is yet another in my series of posts on using JUnit from the perspective of a C# developer. Goals Today, I have the following goals in my quest for JUnit TDD proficiency. Use a BDD-style testing scheme with nested classes. Use mocking framework to verify method call Use mocking framework to verify method call…
