[
https://issues.apache.org/jira/browse/KAFKA-9088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16988210#comment-16988210
]
Guozhang Wang commented on KAFKA-9088:
--------------------------------------
Yeah I had similar experiences with [~ableegoldman], while I feel that whenever
I need to "fix" a test with EasyMock when making a minor change in the code
like a small refactoring, it means that my test is not well written --- it
should be testing the interfaces between classes / modules that are critical
and treated like contracts between these classes. If not then this test is not
useful and should be considered re-written. One example on top of my head are
getters, like how many times you would call such functions, with minor changes
the num.calls of getters may change, but should we really test it in our unit
tests with EasyMock?
> 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)
