[ https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987985#comment-16987985 ]
John Roesler commented on KAFKA-9088: ------------------------------------- Thanks for the justification, [~cadonna]. Since the classes have been a source of maintenance burden, I'm on board with cleaning it up. As noted, my personal experience says that EasyMock would make it harder, not easier, to work with this mock, but of course I also won't object to trying it out! After all, this is the way to know for sure. I think we're on the same page as far as what would constitute an actually simpler end state. Thanks, -John > 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)