I considered that, but it seemed better to keep the MockProcessorContext in test-utils as decoupled as possible from the internals of Streams.
In general, when we're modifying Streams code, we exercise a lot of freedom in modifying internals, and I don't want to risk accidentally changing the behavior of the mock if we decide to add some more stuff to the one used by StreamsPartitionAssigner. If it helps, I can give this one a different name... [ Full content available at: https://github.com/apache/kafka/pull/5567 ] This message was relayed via gitbox.apache.org for [email protected]
