[
https://issues.apache.org/jira/browse/MAHOUT-730?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13048542#comment-13048542
]
Sebastian Schelter commented on MAHOUT-730:
-------------------------------------------
I tried a similar construct, but I don't like it that we have to change our
code for choosing another mocking framework. I also don't like it to make the
result variables instance variables of the class. In my construct I introduced
createKey() and createValue() methods and mocked those, which looks awkward
too. Furthermore I had some problems with writing the same things to a mocked
key/value more than once.
I guess we should just stick with EasyMock, although it's not as elegant as
Mockito, it seems to be better suited for our usecases.
> Replace EasyMock with Mockito
> -----------------------------
>
> Key: MAHOUT-730
> URL: https://issues.apache.org/jira/browse/MAHOUT-730
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.6
> Reporter: Sebastian Schelter
> Assignee: Sebastian Schelter
>
> I'd like to switch our mock library from EasyMock to Mockito. The later one
> needs less code (and doesn't need to be "replayed") and it's more intuitive
> to write tests with it in my experience. Switching shouldn't be a big effort.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
