The power mock/easy mock combo is also quite effective and has one of the cleanest and easiest to understand interfaces I've seen in a mocking library, however I'm not familiar with Jmockit. On Feb 13, 2013 11:42 AM, "Ted Dunning" <[email protected]> wrote:
> For basic mocking, none of the libraries make much difference. Once you > go beyond that, however, there is a world of difference, particularly to do > with mocking static members and methods and the mocking of system classes. > > For example, in testing some fixes to Zookeeper, I needed to mock > System.nanoTime() and System.currentTimeMillies(). This sort of problem > pops up pretty commonly when testing an object in the context of a legacy > environment that wasn't designed for testing. > > For the Zookeeper and mapr-spout, I have been using jmockit with good > results. It can even mock final static system methods. > > > On Feb 12, 2013, at 12:00 PM, Timothy Chen wrote: > > > I was thinking about to use Mocks when I was doing Join earlier, glad > > you've raised this! > > > > I've mostly used Mockito in the past, don't know if there is any a lot > > better option out there. > > > > +1 > > > > Tim > > > > > > On Tue, Feb 12, 2013 at 8:50 AM, Christopher Merrick < > > [email protected]> wrote: > > > >> Hi Team - > >> > >> I'm going to take a stab at putting together some unit tests for a few > of > >> these reference operator implementations that we have built. I don't > see a > >> mocking library imported into the project yet, and I wanted to see if > >> anyone has strong opinions about which to use. I have used mockito in > the > >> past and was generally pretty happy with it - does anyone have a > preference > >> other than this? > >> > >> cheers, > >> Chris > >> > >
