Day 22 of 60
·
E2E, UI, accessibility
Cross-browser / device matrix
The bug only happens on iOS Safari. The bug only happens on a two-year-old Android. The bug only happens in Korea. Cloud farms are the cheapest way to find them before the support tickets do.
ProblemBugs that only appear on Safari/iOS, in older Chrome, or on slow Android phones.
How it works
Run E2E suite across a matrix of browsers and devices. Cloud farms make this tractable; self-hosted is a maintenance burden.
What it catches
WebKit-specific bugs, IE/legacy fallback issues, real-device gestures, locale and font-loading variance.
Tools
BrowserStack · SaaS Sauce Labs · SaaS Playwright cross-browser · OSS
Verdict by project size
Small
Skip
Medium
Opt
Large
Rec
Extra-large
Must
Cost
| Project size | Setup | Maint / mo | Tool / mo | CI / run |
|---|---|---|---|---|
| Small <10k LOC | 4h | 1h | $0 | +2m |
| Medium 10–100k LOC | 2d | 5h | $200 | +8m |
| Large 100k–1M LOC | 8d | 25h | $2k | +20m |
| Extra-large >1M LOC | 25d | 80h | $10k | +40m |
Setup = engineer-days to first useful run ·
Maint = engineer-hours / month at steady state ·
Tool = out-of-pocket $ / month ·
CI = minutes added (or saved) per pipeline run
Lifecycle & ownership
When in lifecycle
Test Release
Per release · Runs before promotion to production.
Who owns it
QA / Test Engineer
Strategy, exploratory, eval design
Collaborates with: Developer
Reference implementations
-
Playwright browsers guide
Cross-browser project configuration and browser-installation patterns.
-
Playwright projects config
Official project matrix pattern for browsers, devices, and configurations.
-
Selenium examples
Cross-browser WebDriver examples across supported languages.
Quick check
Cross-browser / device matrix testing is most cost-effective when run via…
One question. Pick the best answer. Your streak is saved locally on this device.
Save the lesson
Download SVG ↓
Screenshot for a 1:1, drop it in Slack, or download the SVG.