Steve Freeman

Joe Walnes has written up the idea that jMock constraints should be used in jUnit assertions. It reads better and is more flexible.

I’m glad he’s written up such a nice explanation because some of us have felt for ages that this infrastructure belongs in jUnit, rather than in jMock, but it isn’t going to happen.

Happily for .Net developers, the NUnit committers are more accomodating and have taken on some of these ideas from NMock.

Lobby your jUnit committers now!

Update, just added an assertThat() method to the jMock library. It should find its way into the next release.

P.S. I’m posting this on my blog, rather than as a comment on Joe’s, because the MT spam filter has rejected it for “questionable content: dating”. I don’t see it.