Testing Location-Based Features
Override browser geolocation to test store locators, delivery zones, and region-gated content from anywhere.
Store locators, delivery zone calculators, location-based recommendations — these features rely on the browser's Geolocation API. Testing them usually means physically being in the right place, or manually mocking coordinates. Certyn makes this effortless.
How It Works
The agent overrides the browser's geolocation using Chrome DevTools Protocol's Emulation.setGeolocationOverride. Any JavaScript call to navigator.geolocation.getCurrentPosition() will return the coordinates you specify.
No browser extensions. No VPNs. Just tell the agent where you want to be.
Example Scenarios
Test a store locator from New York
"Set location to New York (40.7128, -74.0060) and search for nearby stores. Verify the results show Manhattan locations."
Test delivery zone boundaries
"Set location to the edge of our delivery area and check if the app correctly shows 'delivery available' vs 'out of range'."
Test region-gated content
"Set location to Tokyo (35.6762, 139.6503) and check if the Japanese content version loads correctly."
Test location permission denial
The agent can also clear the geolocation override to test what happens when location access is unavailable — does the app fall back gracefully?
Common Coordinates
Here are some useful locations for testing:
| City | Latitude | Longitude |
|---|---|---|
| New York | 40.7128 | -74.0060 |
| London | 51.5074 | -0.1278 |
| Tokyo | 35.6762 | 139.6503 |
| Sydney | -33.8688 | 151.2093 |
| San Francisco | 37.7749 | -122.4194 |
| Berlin | 52.5200 | 13.4050 |
Tips
- Combine with timezone emulation for a complete regional test
- Test with both precise (accuracy=10) and imprecise (accuracy=5000) locations
- Always test the "location denied" path — many apps forget this case
- Reset the override when done to avoid affecting other tests