Pragmatists/JUnitParams

Parallelize test runs

Open

#84 opened on 2016年6月15日

GitHub で見る
 (5 comments) (2 reactions) (0 assignees)HTML (887 stars) (151 forks)batch import
help wantedreviewed

説明

Could we add a feature for the runner to parallelize test execution (using an executor service based on the available core or whatever policy you deem appropriate)?

I've about 1000 parametrized tests in a single module and while intellij is showing me a total runtime of about 4s, in reality it takes more like 40-50s (i suspect the startup/shutdown harness work, class loading, etc, are at play). These are pure unit tests and do not access outside resources so they are definitely CPU bound and CPU utliziation is only about 30% while running. Suggestions very welcome. Thanks.

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

技術スタック
java
領域
testing
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
half day
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
JavaJUnitconcurrent programming
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
40
調査方針
Explore the JUnitParams runner class and its test execution mechanism. Consider using an ExecutorService to run tests in parallel, as suggested in the issue. Review the existing comments for additional context and potential pitfalls, such as managing test lifecycle and ensuring thread safety. Look at JUnit's parallel test execution features for inspiration.