What has people's experience with EasyMock been?

I am really struggling with it. It seems to encourage reaching inside
classes and programming an explicit list of calls they will make. This
makes the tests very fragile to internal changes.

It also doesn't seem to play all that well with scala due to all the
reflection.

I was originally a big fan since it got us away from massive
non-deterministic integration tests.

But I wonder if we wouldn't be better off just writing simple hand-made
mocks for major classes or increasing the quality of our test harnesses to
do integration testing...?

Thoughts?

-Jay

In particular it breaks some tests between Scala 2.8.0 and 2.9.x due to
changes in Scala's collections impls that impact Map traversal order. I
haven't had any time to work further on the SBT cross-build/upgrade ticket (
https://issues.apache.org/jira/browse/KAFKA-139), but that was definitely a
blocker.

Derek

On Mon, Nov 19, 2012 at 3:38 PM, Jay Kreps <[EMAIL PROTECTED]> wrote:

> What has people's experience with EasyMock been?
>
> I am really struggling with it. It seems to encourage reaching inside
> classes and programming an explicit list of calls they will make. This
> makes the tests very fragile to internal changes.
>
> It also doesn't seem to play all that well with scala due to all the
> reflection.
>
> I was originally a big fan since it got us away from massive
> non-deterministic integration tests.
>
> But I wonder if we wouldn't be better off just writing simple hand-made
> mocks for major classes or increasing the quality of our test harnesses to
> do integration testing...?
>
> Thoughts?
>
> -Jay
>

--
*Derek Chen-Becker*
*Precog Lead Infrastructure Engineer*
[EMAIL PROTECTED]
303-752-1700

I have not tried the KAFKA-139 ticket yet for latest scala but will give
that a try this week. Looks cool.

On Mon, Nov 19, 2012 at 7:11 PM, Derek Chen-Becker <[EMAIL PROTECTED]> wrote:

> In particular it breaks some tests between Scala 2.8.0 and 2.9.x due to
> changes in Scala's collections impls that impact Map traversal order. I
> haven't had any time to work further on the SBT cross-build/upgrade ticket
> (
> https://issues.apache.org/jira/browse/KAFKA-139), but that was definitely
> a
> blocker.
>
> Derek
>
> On Mon, Nov 19, 2012 at 3:38 PM, Jay Kreps <[EMAIL PROTECTED]> wrote:
>
> > What has people's experience with EasyMock been?
> >
> > I am really struggling with it. It seems to encourage reaching inside
> > classes and programming an explicit list of calls they will make. This
> > makes the tests very fragile to internal changes.
> >
> > It also doesn't seem to play all that well with scala due to all the
> > reflection.
> >
> > I was originally a big fan since it got us away from massive
> > non-deterministic integration tests.
> >
> > But I wonder if we wouldn't be better off just writing simple hand-made
> > mocks for major classes or increasing the quality of our test harnesses
> to
> > do integration testing...?
> >
> > Thoughts?
> >
> > -Jay
> >
>
>
>
> --
> *Derek Chen-Becker*
> *Precog Lead Infrastructure Engineer*
> [EMAIL PROTECTED]
> 303-752-1700
>

--

/*
Joe Stein
http://www.linkedin.com/in/charmalloc
Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
*/

I haven't had any time to work on it in a few months, but it's definitely
something I'd like to finish up. I think the last remaining issue is that
SBT isn't integrated into the external packaging scripts, but otherwise it
should work.

Derek

On Mon, Nov 19, 2012 at 9:24 PM, Joe Stein <[EMAIL PROTECTED]> wrote:

> I have not tried the KAFKA-139 ticket yet for latest scala but will give
> that a try this week. Looks cool.
>
> On Mon, Nov 19, 2012 at 7:11 PM, Derek Chen-Becker <[EMAIL PROTECTED]>
> wrote:
>
> > In particular it breaks some tests between Scala 2.8.0 and 2.9.x due to
> > changes in Scala's collections impls that impact Map traversal order. I
> > haven't had any time to work further on the SBT cross-build/upgrade
> ticket
> > (
> > https://issues.apache.org/jira/browse/KAFKA-139), but that was
> definitely
> > a
> > blocker.
> >
> > Derek
> >
> > On Mon, Nov 19, 2012 at 3:38 PM, Jay Kreps <[EMAIL PROTECTED]> wrote:
> >
> > > What has people's experience with EasyMock been?
> > >
> > > I am really struggling with it. It seems to encourage reaching inside
> > > classes and programming an explicit list of calls they will make. This
> > > makes the tests very fragile to internal changes.
> > >
> > > It also doesn't seem to play all that well with scala due to all the
> > > reflection.
> > >
> > > I was originally a big fan since it got us away from massive
> > > non-deterministic integration tests.
> > >
> > > But I wonder if we wouldn't be better off just writing simple hand-made
> > > mocks for major classes or increasing the quality of our test harnesses
> > to
> > > do integration testing...?
> > >
> > > Thoughts?
> > >
> > > -Jay
> > >
> >
> >
> >
> > --
> > *Derek Chen-Becker*
> > *Precog Lead Infrastructure Engineer*
> > [EMAIL PROTECTED]
> > 303-752-1700
> >
>
>
>
> --
>
> /*
> Joe Stein
> http://www.linkedin.com/in/charmalloc
> Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop>
> */
>

--
*Derek Chen-Becker*
*Precog Lead Infrastructure Engineer*
[EMAIL PROTECTED]
303-752-1700