[
https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961475#comment-16961475
]
Sophie Blee-Goldman edited comment on KAFKA-9088 at 10/29/19 7:55 PM:
----------------------------------------------------------------------
[~mjsax] Here's a thought: what if we moved the new
MockInternalProcessorContext to the test-utils package (internal, not public)?
That could help us tackle this issue with unit testing window stores (KAFKA-
[7594|https://github.com/apache/kafka/pull/7594]), as we could provide builder
methods that return an initialized store using the internal processor context,
so that users don't have to rely on internal objects in their own code in order
to get a useable window store
was (Author: ableegoldman):
[~mjsax] Here's a thought: what if we moved the new
MockInternalProcessorContext to the test-utils package (internal, not public)?
That could help us tackle this issue with unit testing window stores
(KAFKA-9088), as we could provide builder methods that return an initialized
store using the internal processor context, so that users don't have to rely on
internal objects in their own code in order to get a useable window store
> 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)
