You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had a look at junit5 about parallel and way its implemented there is the annotation declaration for suite or test methods. In their implementation it allows for permutations of parallel suites or test methods.
I think we should start with an annotation on the suite to parallelize all tests under it. Author is responsible for making them paralell safe.
So the suites will call serially but tests within suites that is annotated would run parallel.
The results would have to be stored in the table as the chunks will be run by different sessions.
The sample annotation couls looks like --%parallel(4)
In case of nested suite the parallel wil be inherited to child suites. The child suites will be run serial however the tests within these suites will run parallel as defined by parent suite.
We will have to make sure that coverage data will be linked to same runid or at least we are able to merge them from child session to coordinator session, same goes for reporting.
This discussion was converted from issue #881 on May 09, 2026 17:18.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Consider enable of parallelism inside framework using dbms parallel, job_chains etc.
What are pros and cons.
All reactions