[KAFKA-6473] Add MockProcessorContext to public test-utils

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.1.0
• Fix Version/s: 2.0.0
• Component/s: streams
• Labels: kip user-experience
• Assignee: John Roesler
• Reporter: Matthias J. Sax
• Created: 23/Jan/18 20:02
• Updated: 25/Apr/18 09:42
• Resolved: 27/Mar/18 21:05

Description

With KIP-247, we added public test-utils artifact with a TopologyTestDriver class. Using the test driver for a single Processor/Transformer/ValueTransformer it's required to specify a whole topology with source and sink and plus the Processor/Transformer/ValueTransformer into it.

For unit testing, it might be more convenient to have a MockProcessorContext, that can be used to test the Processor/Transformer/ValueTransformer in isolation. Ie, the test itself creates new Processor/Transformer/ValueTransformer object and calls init() manually passing in the MockProcessorContext.

This is a public API change and requires a KIP: https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Improvement+Proposals

Issue Links

• is related to: KAFKA-3625 Move kafka-streams test fixtures into a published package
• relates to: KAFKA-5739 Rewrite KStreamPeekTest at processor level avoiding driver usage
• links to: GitHub Pull Request #4736
• mentioned in: Page Loading...
• mentioned in: Page Loading...