You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2024/04/10 03:10:00 UTC
[jira] [Resolved] (KAFKA-16487) Support to define server properties by ClusterTestDefaults
[ https://issues.apache.org/jira/browse/KAFKA-16487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chia-Ping Tsai resolved KAFKA-16487.
------------------------------------
Fix Version/s: 3.8.0
Resolution: Fixed
> Support to define server properties by ClusterTestDefaults
> ----------------------------------------------------------
>
> Key: KAFKA-16487
> URL: https://issues.apache.org/jira/browse/KAFKA-16487
> Project: Kafka
> Issue Type: Test
> Reporter: Chia-Ping Tsai
> Assignee: PoAn Yang
> Priority: Minor
> Fix For: 3.8.0
>
>
> Sometimes we want to define server properties for all test cases, and using `BeforeEach` to modify the `ClusterConfig` is the only way. The side effect is that the IDE does not like the style since IDE can't recognize custom ParameterResolver of `ClusterConfig`.
> The alternative is that we can take `ClusterInstance` from constructor first, and then we modify the inner `ClusterConfig` in `BeforeEach` phase. However, that may confuse users about the life cycle of "configs".
> In short, I prefer to define the server property by `ClusterTestDefaults`. It already includes some server-side default property, and we can enhance that to deal with more existent test case.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)