qa-cell-worker

Parallel browser testing for large route and viewport matrices is executed by dispatching assigned QA audit cells to isolated browser workers. This prevents cross-worker interference while sequentially processing chunks of audit cells to maintain per-cell coverage.

A QA audit cell in frontend automation represents a specific combination of route, viewport, and browser targets for isolated testing. It requires per-cell navigation, probing, and screenshot capture to verify application behavior across different environments.

Parallel QA testing works with Chromium, Firefox, and WebKit by assigning dedicated MCP browser servers to each worker. This ensures deterministic evidence collection across different browser engines without corrupting shared state.

To deduplicate issue logging during automated browser audits, probe and interactive results are written to dedicated .tmp/{runId}/issues/ files. This coverage-safe receipt mechanism ensures downstream annotation and bug filing can rely on the findings.

The best way to handle login and redirects during parallel execution is using a resilient QA workflow within each isolated browser worker. This manages authentication, data readiness, and timeout recovery independently per assigned cell.

You need an orchestrator to split a QA run across multiple workers to coordinate the assignment of audit cells to isolated browser instances. The worker then independently executes the assigned probes and records findings for that specific chunk.