Mockito... You also want to get yourself a copy of Michael Feathers' "working with legacy code" book. On 2 Mar 2011 20:23, "B Smith-Mannschott" <[email protected]> wrote: > Hi Posse, > > I have some experience with unit testing on smaller projects, but have > not used a mocking framework "in anger". At work, we'll be building a > new section of our main application on a new foundation and are > determined that the new code be well tested. (The rest of the > application is a 10-year-old ball-of-mud.) Our data model is complex > enough that it makes sense to adopt a solution for mocking and > stubbing. What do you recommend? What do you consider important in a > mocking library? > > I've done some research, and I'm leaning toward Mockito, but really, I > don't know what I'm talking about. Do any of you have war stories you > can share? Have any of you chosen a particular mocking framework, and > then regretted it? Please share your experience. > > I'd also like to finally make the jump from junit 3.8 to 4.8, and > there's something I'm not at all clear on. I've seen examples of > hamcrest matchers to record expectations in "modern" junit tests. How > much overlap is there between Hamcrest and a mocking library such as > Mockito? > > Thanks, > Ben > > -- > You received this message because you are subscribed to the Google Groups "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/javaposse?hl=en. >
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
