Enable parallel run of test within a suite
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
Start by checking the project’s test sources to locate the suite class(es) intended to run in parallel and inspect their current base classes/traits. Read the existing test setup so you can safely add FixtureAnyFunSuite and ParallelTestExecution in the right place. Then run the test command (likely sbt test) to verify behavior and ensure all tests still pass. Done means the target suite is parallelized and the suite remains green.
Written by the indexing model from the issue text.
Description
Feature Description
For better performance, if desired, allow parallel run of tests within a suite.
Proposed Solution
Use FixtureAnyFunSuite and ParallelTestExecution traits as the basis for the class.
Dependencies / Related
No response
Additional Context
No response
- Dominant language
- Scala
- Stars
- 3
- Forks
- 2
- Avg merge
- 14h 48m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AbsaOSS/balta
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
enhancement tech debt
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
enhancement refactoring
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
documentation good first issue
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
ergoplatform/ergodocs#614 ·
-
area:ci enhancement requires-triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
apache/datafusion-comet#6078 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
[VL] madvise(WILLNEED) call fails in MmapFileStream because of wrong calculation of fetching length Openbug triage
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
chipsalliance/rocket-chip#3831 ·