Are there any strategies that others are using to split affected tests in parallel runs (we are using CircleCI but looking for a general method I can adapt)
Here is a Jenkins example from the nrwl team: https://github.com/nrwl/nx-jenkins-build
It leverages the
print-affected command to list out affected targets and then distributes those over multiple nodes
Specific example: https://github.com/nrwl/nx-jenkins-build#distributed-setup
We haven’t implemented this yet but are thinking about it
Awesome thanks! We are currently splitting app tests and lib tests between parallel runs but i would like to split the tests into more than one.
Yeah this example gives that kind of fine-grained control, in addition to allowing you to specify how many targets to run per node :eyes: so cool!