[Feature] UT Phase Takes Too Long During CI Execution, Needs Analysis and Optimization · apache/dubbo#15492

2025-06-26T01:48:13.000Z

### Pre-check - [x] I am sure that all the content I provide is in English. ### Search before asking - [x] I had searched in the [issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no similar feature requirement. ### Apache Dubbo Component Java SDK (apache/dubbo) ### Descriptions In the current Dubbo CI process, the unit test (UT) phase takes a relatively long time, which affects overall efficiency during development and PR submissions. We need to: - [ ] Which modules are the most time-consuming during UT? - [ ] Are there any redundant tests or inefficient test cases? - [ ] Is the lack of parallelism slowing down the test execution? Any suggestions or contributions are welcome! ### Related issues _No response_ ### Are you willing to submit a pull request to fix on your own? - [ ] Yes I am willing to submit a pull request on my own! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

(5 comments) (0 reactions) (2 assignees)Java (26,453 forks)batch import

good first issuetype/enhancementtype/proposal

Repository metrics

Stars: (41,524 stars)
PR merge metrics: (平均マージ 8d 4h) (30d で 31 merged PRs)

説明

Pre-check

I am sure that all the content I provide is in English.

Search before asking

I had searched in the issues and found no similar feature requirement.

Apache Dubbo Component

Java SDK (apache/dubbo)

Descriptions

In the current Dubbo CI process, the unit test (UT) phase takes a relatively long time, which affects overall efficiency during development and PR submissions. We need to:

Which modules are the most time-consuming during UT?
Are there any redundant tests or inefficient test cases?
Is the lack of parallelism slowing down the test execution?

Any suggestions or contributions are welcome!

Related issues

No response

Are you willing to submit a pull request to fix on your own?

Yes I am willing to submit a pull request on my own!

Code of Conduct

I agree to follow this project's Code of Conduct

コントリビューターガイド

調査方針: まず、CI ワークフローの設定ファイル（例：.github/workflows/ci.yml）を確認し、現在のテスト実行のセットアップを理解します。次に、Maven モジュール構造を調べ、テスト時間が最も長いモジュールを特定します（ビルドレポートを使用する可能性があります）。この課題の担当者やコメント投稿者と連携し、これまでの分析や提案されたアプローチに関する知見を収集します。
技術スタック: java
領域: backendci cdtesting
Issue 種別: 機能
難度: 4
推定時間: 3-5日
活動状況: アクティブ
明確さ: おおむね明確
前提条件: Java programmingMaven build toolUnit testing conceptsApache Dubbo basic understanding
初心者向け度: 50