Wondering what it would take for dusk tests to be able to run in parallel. Huge dusk test suite is a pain, it takes almost an hour to run.
•
Back
There is no such option for Dusk, you have to do it all by hand, and it's a bit of a chore. I've also had to setup separate chrome driver instances in my case.
Maybe one day I will get some time to hack on this and make a PR that makes it easier.
you'd need to create separate test suites to only run a subset of the Dusk tests. You'd also need separate databases, so that they don't interfere with each other.
•
That's the strategy I've adopted until now. But for unit & feature tests, the `--parallel` cli option seems to automatically give you the separate databases setup: laravel.com/docs/11.x/testing#parallel-testing-and-databases
There is no such option for Dusk, you have to do it all by hand, and it's a bit of a chore. I've also had to setup separate chrome driver instances in my case.
Maybe one day I will get some time to hack on this and make a PR that makes it easier.
•
Correct, and I agree. I have a Github Action workflow with a matrix. So everything is set up separately.
I remember an interesting Over Engineered podcast that touched upon running dusk in parallel with ReactPHP.
Think it was this one
overengineered.fm/episodes/reactphp-event-loops-w-len-woodward
•