You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Ning Zhang (Jira)" <ji...@apache.org> on 2020/08/26 03:32:00 UTC

[jira] [Updated] (KAFKA-10304) Revisit and improve the tests of MirrorMaker 2

     [ https://issues.apache.org/jira/browse/KAFKA-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ning Zhang updated KAFKA-10304:
-------------------------------
    Component/s: mirrormaker

> Revisit and improve the tests of MirrorMaker 2
> ----------------------------------------------
>
>                 Key: KAFKA-10304
>                 URL: https://issues.apache.org/jira/browse/KAFKA-10304
>             Project: Kafka
>          Issue Type: Test
>          Components: KafkaConnect, mirrormaker
>            Reporter: Ning Zhang
>            Assignee: Ning Zhang
>            Priority: Minor
>
> due to the quick development of Kafka MM 2, unit and integration tests of MirrorMaker 2 were made just for covering each individual feature and some of them are simply copy-n-paste from the existing tests with small tweaks. It may be a good time to revisit and improve the tests, possibly in the following way:
> (1) are 100 messages good enough for integration tests?
> (2) what about the failure in the middle of integration tests?
> (3) Do we want to check other messages (e.g. checkpoint, heartbeat, offset sync..) beyond the mirrored message in integration tests?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)