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
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
> 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...?
*Precog Lead Infrastructure Engineer*