Optimize run time on Behat on GitHub Actions
Nobody likes to wait period, but nobody likes to wait especially for a pipeline to finish so they can see if their behat test failed.
GitHub Action’s run time is always a little hard to predict because unless you run your workflows on dedicated (self-hosted) instances you are effectively at the mercy of GitHub VM distribution.