Modern QA2026Parallel Execution in CI — tiles
Log inJoin
90 / 168 · 01 Agent Skills for Browser Automation · CI/CD Integration for AI-Driven Browser Tests← prev⊞ allnext →☰ Read as one page

12.5Parallel Execution in CI

Matrix Strategy (GitHub Actions)

strategy:
  fail-fast: false
  matrix:
    test-group: [auth, dashboard, checkout, settings, admin]

Each test group runs as a separate job with its own browser instance. fail-fast: false ensures all groups run even if one fails.

Within a Single Job

# Run 4 tests in parallel — isolation comes from one named session per test
cat test_list.txt | xargs -P4 -I{} bash -c '
  ./run-single-test.sh "{}"     # opens/closes playwright-cli -s="{}"
'

Resource Limits

Workers RAM Needed CPU Needed
1 ~200MB 1 core
4 ~800MB 4 cores
8 ~1.6GB 8 cores

CI runner recommendation: 4 parallel workers on a standard 2-core runner (the browser is mostly I/O-bound, not CPU-bound).