Chia-Ping Tsai created KAFKA-20350:
--------------------------------------
Summary: Consolidate and clarify boundaries of TestUtils classes
across modules
Key: KAFKA-20350
URL: https://issues.apache.org/jira/browse/KAFKA-20350
Project: Kafka
Issue Type: Improvement
Reporter: Chia-Ping Tsai
Assignee: Chia-Ping Tsai
from [https://github.com/apache/kafka/pull/21679#issuecomment-4113577448]
To improve maintainability and keep our dependency graph clean, we should
consolidate these utilities and establish clear boundaries. Based on our
current project structure, I propose we limit the general {{TestUtils}} to the
following three foundational modules:
* {*}{{clients}}{*}: For client-related testing utilities.
* {*}{{server-common}}{*}: For broker/server-side utilities. Since modules
like {{{}storage{}}}, {{{}raft{}}}, and {{metadata}} already depend on
{{{}server-common{}}}, this prevents cyclical dependencies and visibility
workarounds.
* {*}{{test-common-runtime}}{*}: Strictly limited to internal use. While it
provides JUnit extensions and test infrastructure, {*}other modules cannot
import or reference its classes directly{*}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
