Cross-browser testing: Chromium, Firefox, WebKit, measured
Cross-browser testing runs the same journey in more than one engine because the engines differ: in default fonts and scrollbars, in which inputs they render natively, in how they treat a download, and in what their automation layer reports. Most differences are harmless; a few break a test or a user, and the only way to know which is to run the page.
This hub is built from runs rather than claims. The cross-browser guide reports what each of Chromium 151, Firefox 153 and WebKit 26.5 said about one page; the download guide reports an engine difference that stopped a test outright; the selector guide reports a tenfold positional-selector cost in one engine. The recorder runs five engines; the integration page says which features are engine-specific.
What people search for
The literal queries this hub is written to answer; each leads to one of the pages below.
- cross browser testing
- playwright cross browser testing
- cross browser testing tools
- automated testing for multiple browsers
- safari testing on linux
- browser compatibility testing
Do it: what the engines actually differ on
Executed guides.
Cross-browser testing with Playwright
Thirty facts from one page in three engines, and which ones matter to a test.
How to test file downloads
The attachment link that raised no download event in WebKit.
XPath vs CSS selectors
A 111 ms positional lookup in WebKit against 0.3 ms in Chromium.
Learn
The concepts.
Cross-browser testing
What it is and what it is not (device testing).
Visual regression
The way to see what differs rather than guess.
Prove it
Five engines in the product.
The test recorder
Chromium, Chrome, Firefox, WebKit and Edge; scheduled folder runs use Chromium.
Dokimore vs BrowserStack
Where a device cloud is the right answer.
Code export
Run the same exported test in every project of your own config.
Questions people ask
Do I need to test in every browser?
Test where your users are, and at least once in each engine family: a Chromium browser, Firefox and WebKit (Safari). The engines differ in ways a Chromium-only run cannot show; the cross-browser guide on this page lists the ones measured in one run, from default fonts to a download that never raised its event.
Can I test Safari without a Mac?
Playwright drives WebKit, Safari’s engine, on Linux and Windows, which catches engine-level differences; it is not Safari itself, so a release still deserves a check in the real browser. The recorder’s WebKit engine is that same build.
Is cross-browser testing the same as device testing?
No. Cross-browser testing varies the engine; device testing varies the screen, the touch input and the operating system, usually on a cloud of real devices. The BrowserStack comparison says plainly when a device cloud is the right purchase.
Try it on your own application
The Free plan asks for no card and runs for 14 days after the trial: record a flow, replay it, and read the evidence each step produced.