Add support for additional parallel configuration #85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Initial feedback for the parallel mode was that depedending on the project under test how features were split across them could be quite unbalanced.
For example in a project with some features containing only one scenario, and others containing lots you could end up waiting for one process to finish because the others got the features with only a few scenarios. So the ability to tell ParallelTests to group by 'scenarios' would be really beneficial.
The other was that depending on your machine you may get some benefit increasing the number of processes running.
Hence this change expands the parallel config from a simple
parallel: true
to a whole new section in theconfig.yml
, and addss support into Quke to process the additional arguments.