Device emulation and mobile networking are different tests
Browser emulation changes client-environment parameters. A mobile proxy changes the network path. Reliable testing treats these as separate axes and then combines them.
Key points in one minute
- Browser geolocation does not prove IP geography.
- A user agent does not prove a physical device.
- A four-run baseline matrix separates interface and routing defects.
- Every conclusion in a report should rely on the matching independent signal.
What Playwright emulates
A device profile sets viewport, screen size, touch, and user agent; locale, timezone, permissions, and geolocation are configured separately.
Record the browser version and device profile together with viewport, deviceScaleFactor, touch, locale, and timezone. State the expected effect of each setting: responsive layout depends on viewport width, while date formatting depends on locale. This prevents the false conclusion that one mobile-device switch reproduces an entire physical handset.
What the proxy changes
A proxy determines the connection path and outbound address visible to the destination. It does not automatically change screen size, language, or browser coordinates.
Confirm the network route through a separate authorized endpoint and retain the returned country or region, a pseudonymous egress identifier, and check time. Do not infer a person's precise location from an IP address or mix IP geography with browser coordinates. When signals disagree, report both values rather than hiding the mismatch.
A test matrix
Compare desktop and mobile viewports over direct and mobile routes. This separates responsive-layout defects from network or regional issues.
A minimum matrix has four runs: desktop and mobile viewports over direct and mobile routes. Predefine identical steps, test data, and criteria such as response status, no horizontal overflow, key-action latency, and correct regional content. Expand the matrix only after the baseline is stable, or combinatorial growth will obscure the root cause.
Recording results
Report device profile, viewport, locale, timezone, permissions, and verified outbound IP as independent parameters.
Store a configuration ID, timestamp, scenario version, and independent device and network facts in the result artifact. Screenshots help with layout but do not prove routing; an outbound address helps with networking but does not prove touch behavior. Remove secrets, cookies, and the user's full address before publishing or sharing the report.
Practical checklist
- 1Do not describe emulation as a physical device.
- 2Verify the outbound address separately.
- 3Keep a configuration matrix.
- 4Record the browser version and configuration ID.
- 5Remove cookies and exact addresses from artifacts.
Sources and documentation
This material is based on primary, official, and technical sources. The article is an original summary written for this knowledge base.