[
https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16966650#comment-16966650
]
Bruno Cadonna commented on KAFKA-9088:
--------------------------------------
Just to be clear. I did not say that we cannot change {{MockProcessorContext}}.
I said that without a KIP we must ensure that the API and the behaviour of the
MockProcessorContext stays the same.
If you try the EasyMock solution, could you please try to bundle shared code
instead of repeating the same setups in tests again and again. Would a wrapper
around an EasyMock maybe work in this case?
> 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
> 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)
