Let’s just say it’s painful. More to come!
Another day, another failure to make FitLibrary do what I’m asking it to do. I’ve been trying off and on for about a month now to implement double comparisons with tolerances, and every time I think I’ve made progress it … Continue reading →
n. The feeling one has at the end of a day spent failing to get something to work
Sometimes it’s necessary to ask someone several questions. It has been my experience that there is a better-than-even chance that an email containing more than one question will trigger a return email with a response to one question. This applies outside … Continue reading →
It happens. You find a framework, it’s extremely promising. Then you hit a problem and it falls apart. FitLibrary – and by extension FitNesse, since FitLibrary is key to making FitNesse easier to use – falls apart at the point … Continue reading →
I just wrote my first test with a Mockito mock, and I got confused for just a second writing it. First up is import syntax: import static org.mockito.Mock.*; That static specifier is key. They tell you that right up front, … Continue reading →
Right now I’m playing around with Java and FitNesse and some related tools, and I’m starting to be comfortable with at least those first two, so it seems like a good moment to stop and reflect. One of the pieces … Continue reading →