[
https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988579#comment-16988579
]
Bruno Cadonna commented on KAFKA-9088:
--------------------------------------
I understand all your concerns and sometimes I also had hard times with
EasyMock. However, I think the issues are only partly caused by EasyMock. The
design of the production code may leak internals, the unit test may have issues
because it tests too much or the wrong aspects, and EasyMock may be used
wrongly. For instance, sometimes it does not make sense to specify how often a
method on the mock is called or if it is called at all. That would be the case
for the {{InternalProcessorContext}} mock and EasyMock offers functionality
that allows to specify that. I would like to explore this part of EasyMock in
this ticket.
> Consolidate InternalMockProcessorContext and MockInternalProcessorContext
> -------------------------------------------------------------------------
>
> Key: KAFKA-9088
> URL: https://issues.apache.org/jira/browse/KAFKA-9088
> Project: Kafka
> Issue Type: Improvement
> Components: streams, unit tests
> Reporter: Bruno Cadonna
> Assignee: Pierangelo Di Pilato
> Priority: Minor
> Labels: newbie
>
> Currently, we have two mocks for the {{InternalProcessorContext}}. The goal
> of this ticket is to merge both into one mock or replace it with an
> {{EasyMock}} mock.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
