Pragmatists/JUnitParams

Parallelize test runs

Open

#84 opened on Jun 15, 2016

View on GitHub
 (5 comments) (2 reactions) (0 assignees)HTML (887 stars) (151 forks)batch import
help wantedreviewed

Description

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.

Contributor guide

Tech stack
java
Domain
testing
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
JavaJUnitconcurrent programming
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.