Awesome! Is there a reason why you decided to go with just 2 parallel jobs? What are the odds of setting that number higher?

I think setting that number higher (more parallel jobs) could be faster, we found 2 parallel jobs are adequate enough for our company hence we just used 2

How do you consolidate the test results into a readable format?

Hi Kurt, if you mean test coverage, I have written an article on how to merge it from parallel test ( running on CircleCI) here : https://rubyyagi.com/merge-... , you can change the "CIRCLE_NODE_INDEX" to "CI_NODE_INDEX" to make it work with Github Actions, hope this helps!

I work on similar problem, also to automatically split slow RSpec test files into parallel jobs on Github Actions. For instance if you have feature spec taking a few minutes then individual test examples can be run in parallel jobs. Here is github actions example https://docs.knapsackpro.co...