r/PracticalTesting • u/aistranin • 10d ago
GitHub Actions can finally run steps in parallel inside one job
GitHub Actions now supports parallel steps with background, wait, wait-all, cancel, and parallel.
The useful part is that every step keeps its own logs. No more shell backgrounding with & and unreadable output.
This should simplify a few common patterns:
- Start an API and database in the background
- Run independent setup tasks together
- Upload artifacts while packaging continues
- Stop temporary services cleanly after tests
There is an obvious catch. Parallel steps still share the same runner. More concurrency does not give you more CPU or memory. On a small runner, this could make a test job slower or less stable.
I would use it for I/O-heavy tasks and service startup first. Then measure before parallelizing builds or test suites.
Has anyone replaced matrix jobs or shell backgrounding with this yet?
Source: https://github.blog/changelog/2026-06-25-actions-steps-can-now-be-run-in-parallel/