tag:blogger.com,1999:blog-9944221.post2242805514296690712..comments2023-11-03T06:15:55.087-05:00Comments on Meme Agora: Mocking JRubyNeal Fordhttp://www.blogger.com/profile/12839796402858974817noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-9944221.post-58107996020296228812007-10-24T16:37:00.000-05:002007-10-24T16:37:00.000-05:00Seconding Nat (of course). The most relevant part ...Seconding Nat (of course). <BR/><BR/>The most relevant part of a dynamic language is the doesNotUnderstand/missingMethod (or whatever it is in Ruby) hook. Tim Mackinnon's Smalltalk mock library is a model of brevity because of the use he could make of blocks.Steve Freemanhttps://www.blogger.com/profile/14771999065792016571noreply@blogger.comtag:blogger.com,1999:blog-9944221.post-69404776340388211502007-10-21T17:42:00.000-05:002007-10-21T17:42:00.000-05:00I'm not sure about cleaner, easier mocks. The exp...I'm not sure about cleaner, easier mocks. The expectations in the code above are more cryptic than those in jMock 2.<BR/><BR/>I find that surprising because Ruby's blocks would make it much easier to use real method calls to describe expectations, compared to the hoops we had to jump through to write the jMock 2 API.Nat Prycehttps://www.blogger.com/profile/14593335423887511402noreply@blogger.comtag:blogger.com,1999:blog-9944221.post-64344701036841694772007-10-21T07:12:00.000-05:002007-10-21T07:12:00.000-05:00Refactoring is generally weaker in Ruby (although ...Refactoring is generally weaker in Ruby (although getting better, I doubt it will ever be as good as Java or other static languages). Thus, this code is harder to refactor than the corresponding jMock code. But, you can't have everything, so you get to pick: cleaner, easier mocks with a dynamic language or refactorability with jMock.Neal Fordhttps://www.blogger.com/profile/12839796402858974817noreply@blogger.comtag:blogger.com,1999:blog-9944221.post-69398290485519252007-10-18T03:34:00.000-05:002007-10-18T03:34:00.000-05:00What about refactoring? The biggest complaint abo...What about refactoring? The biggest complaint about jMock 1 (now addressed in jMock 2) was that expectations were difficult to refactor. Doesn't this approach of using JRuby extend that problem to the entire test suite?Nat Prycehttps://www.blogger.com/profile/14593335423887511402noreply@blogger.com