[
https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988913#comment-16988913
]
John Roesler commented on KAFKA-9088:
-------------------------------------
Thanks, Bruno, I don’t want you to feel besieged. It seems like this
conversation has yielded a good list of common pitfalls with EasyMock, but at
the end of the day the only way to know for sure is to try to make it work.
It should be obvious from the diff whether it really makes things easier or
not. As long as it’s approached in the spirit of a prototype, it shouldn’t be
too frustrating to just take another stab at the implementation.
Just one specific thought... It may be possible that some tests don’t need a
rich interaction with the context. In those cases, maybe they can just create a
mock inline. This might free up some of the constraints to simplify
MockInternalProcessorContext for use with just the tests that need a more
complex interaction. I.e., sometimes trying for a general drop-in replacement
isn’t necessary, and just complicates everything.
> 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)
