You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Paolo Patierno (JIRA)" <ji...@apache.org> on 2017/08/16 13:28:00 UTC

[jira] [Created] (KAFKA-5739) Rewrite KStreamPeekTest at processor level avoiding driver usage

Paolo Patierno created KAFKA-5739:
-------------------------------------

             Summary: Rewrite KStreamPeekTest at processor level avoiding driver usage
                 Key: KAFKA-5739
                 URL: https://issues.apache.org/jira/browse/KAFKA-5739
             Project: Kafka
          Issue Type: Test
          Components: streams
            Reporter: Paolo Patierno
            Assignee: Paolo Patierno
            Priority: Minor


Hi,
as already done for the {{KStreamPrintTest}} we could remove the usage of {{KStreamTestDriver}} even in the {{KStreamPeekTest}} and testing it at processor level not at stream level.
My proposal is to :

* create the {{KStreamPeek}} instance providing the action which fill a collection as already happens today
* testing for both {{forwardDownStream}} values true and false
* using the {{MockProcessorContext}} class for overriding the {{forward}} method filling a streamObserved collection as happens today {{forwardDownStream}} is true; checking that the {{forward}} isn't called when {{forwardDownStream}} is false (so the test fails)

Thanks,
Paolo 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)