[
https://issues.apache.org/jira/browse/KAFKA-18517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17912915#comment-17912915
]
黃竣陽 edited comment on KAFKA-18517 at 1/14/25 2:04 PM:
------------------------------------------------------
There are the test classes, which have some test cases only test the classic
protocol
- SaslClientsWithInvalidCredentialsTest
- ConsumerBounceTest
- PlaintextAdminIntegrationTest
- GssapiAuthenticationTest
- MultipleListenersWithSameSecurityProtocolBaseTest
- SaslClientsWithInvalidCredentialsTest
was (Author: JIRAUSER305187):
There are the test classes
- SaslClientsWithInvalidCredentialsTest
- ConsumerBounceTest
- PlaintextAdminIntegrationTest
- GssapiAuthenticationTest
- MultipleListenersWithSameSecurityProtocolBaseTest
- SaslClientsWithInvalidCredentialsTest
> ConsumerBounceTest should run for async consumer
> ------------------------------------------------
>
> Key: KAFKA-18517
> URL: https://issues.apache.org/jira/browse/KAFKA-18517
> Project: Kafka
> Issue Type: Test
> Components: consumer
> Reporter: Lianet Magrans
> Assignee: Lianet Magrans
> Priority: Blocker
> Labels: kip-848-client-support
> Fix For: 4.0.0
>
>
> All tests in the file are parametrized to run for Classic only, so they won't
> run with the new async consumer. We should enabled them so that they run both
> both consumers.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
