Geo-testing and localisation QA

The problem

Localisation bugs only show up from the right network: a geo-redirect that loops for one carrier, a consent banner missing in one country, a CDN edge serving stale content to mobile users.

QA teams need a reproducible way to browse as a mobile user in each market, from the CI pipeline and from a tester's own browser.

Configuration

Product

Dedicated mobile proxy per country under test, 7 or 30 days

Carrier

The carrier with the largest market share, or each carrier for CDN tests

Rotation

Rotation link called between test runs

Authentication

IP whitelist for CI runners, username and password for testers

Devices

Phones through Wi-Fi proxy settings, emulators and headless browsers

Checks

Redirects, currency and language, consent banners, CDN headers

Example

PROXY="http://m_k3v9q2xa:[email protected]:10421"

curl -s -x "$PROXY" https://ipinfo.io/json

curl -s -o /dev/null -w "%{http_code} %{redirect_url}\n" \
     -x "$PROXY" -A "Mozilla/5.0 (Linux; Android 14)" \
     https://www.example.com/

curl -s "https://proxuno.com/rotate/3f9c1a7e5b2d4c6f8a0e1b3d5f7a9c2e"
sleep 10

Example credentials. Replace them with yours from the dashboard.

Best practices

• Assert on the exit IP's country at the start of each test run so a misconfigured proxy fails fast.
• Test each major carrier at least once per release — CDNs and redirects can differ per network.
• Keep rotation outside the test: rotate between runs, never in the middle of a scenario.
• Whitelist your CI runners' IPs instead of storing proxy passwords in pipeline variables.