HI Ben. I'm pretty new to this too but I've been happily using Mockito for a while now. I was having the same dilemma as you (which to choose with no experience to back my choice up) and so I asked a more experienced friend for his recommendation. As somebody else pointed out, there's really not much choice out there. One thing that helped me decide right away is that Mockito allows for mocking concrete classes, whereas you have to use an extension to get that with JMock. Being able to mock a concrete class is indispensable with a ball-of- mud app.
The other thing I love with Mockito is that it has really helpful error messages. When Mockito throws an exception it will usually tell you almost exactly what went wrong. That helps a lot with the initial learning curve. Mockito's syntax reads sort of like a DSL, so that's a bonus as well. Good luck. -- 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.
