[
https://issues.apache.org/jira/browse/KAFKA-15764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17781377#comment-17781377
]
Justine Olshan commented on KAFKA-15764:
----------------------------------------
It should be sufficient to add parameterizations on a test where we add
compression types to the records we produce. I think this may be possible to do
in system tests.
Here's a test that uses compression types already. I wonder if we could add
this parameterization to transactions_test.py
[https://github.com/apache/kafka/blob/7bdd1a015e2a91192c0ea07b39bd4d9195472763/tests/kafkatest/tests/core/compatibility_test_new_broker_test.py#L71]
> Missing tests for transactions
> ------------------------------
>
> Key: KAFKA-15764
> URL: https://issues.apache.org/jira/browse/KAFKA-15764
> Project: Kafka
> Issue Type: Test
> Affects Versions: 3.6.0
> Reporter: Divij Vaidya
> Assignee: hudeqi
> Priority: Major
>
> As part of https://issues.apache.org/jira/browse/KAFKA-15653 we found a bug
> which was not caught by any of the existing tests in Apache Kafka.
> However, the bug is consistently reproducible if we use the test suite shared
> by [~twmb] at
> https://issues.apache.org/jira/browse/KAFKA-15653?focusedCommentId=17777846&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17777846
>
> As part of this JIRA, we want to do add relevant test in Apache Kafka which
> should have failed. We can look at the test suite that franz/go repository is
> running, more specifically the test suite that is executed by "go test -run
> Txn".(see repro.sh attached to the comment linked above).
> With reference to code in repro.sh, we don't need to do docker compose down
> or up in the while loop Hence, it's ok to simply do
> ```
> while go test -run Txn > FRANZ_FAIL; do
> done
> ```
> The exit criteria for this Jira should be to have a test in Apache Kafka
> which will fail on 3.6.0.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
