Your checkout flow works perfectly in your local dev environment. Ship it to production, and suddenly users in Brazil are seeing different prices, users in the EU get GDPR banners that break the layout, and users in China can't load the page at all.
This is the reality of building for a global audience. And until now, testing it meant setting up VPNs, begging friends in other countries to click around, or just hoping for the best.
We just shipped geolocation testing.
What this solves
Pick a country from the dropdown, and your entire test runs as if the browser is physically located there. The target site sees an IP address from that country, serves country-specific content, and your AI agent tests exactly what your users see.
This catches things like:
- Geo-blocked content - Pages that only load in certain regions
- Localized pricing - Different currencies, prices, or payment methods by region
- Regional compliance banners - GDPR in EU, CCPA in California, cookie consent everywhere
- CDN and edge behavior - Content served from regional edge nodes
- Language redirects - Sites that auto-redirect based on IP location
How we built it
We started with BrightData datacenter proxies - 110+ countries, consistent uptime, fast connections. When you select a country in Test-Lab, we route your test traffic through a proxy network. The target site sees an IP from that country. Everything else works exactly the same - your AI agent still sees the full page, takes screenshots, and reports results.
BrightData worked well for most sites. But some geo-restricted sites (streaming services, certain e-commerce platforms) were detecting and blocking datacenter IPs.
Update: We've since added NordVPN integration as our primary provider for geo-restricted content. VPN IPs look residential rather than datacenter, so they don't trigger the same blocks. BrightData remains available as a fallback. Read the NordVPN post for the technical details.
Using your own proxy
We now use NordVPN as the primary provider (with BrightData as fallback), but the underlying Playwright configuration supports custom proxy providers too. If your company already has a proxy solution you trust, we can configure Test-Lab to use it.
This is useful for:
- Corporate VPNs - Test as if you're inside your company network
- Residential proxies - Your own residential proxy provider
- Custom proxy chains - Specific routing requirements
Reach out if you need a custom proxy setup. We can work with most HTTP/HTTPS proxy providers.
Setting it up
You can configure geolocation at two levels:
Project-level default: Set a default country for all test plans in a project. Go to Projects, edit a project, and select a country from the Location dropdown. All test plans in that project will use this location unless overridden.
Test plan-level override: Individual test plans can override the project default. When editing a test plan, expand Advanced Settings and select a different country if needed.
This hierarchy makes it easy to test an entire project from a specific region while still allowing exceptions for specific test plans.
The default is United States, which is where our test servers are located. Selecting US means no proxy is used - it's the fastest option and good for most tests.
Pick any other country, and we route through BrightData automatically. Scheduled runs and API triggers all respect these location settings.
110+ countries supported
We support basically everywhere BrightData has coverage:
Major markets: United States, United Kingdom, Germany, France, Canada, Australia, Japan, Brazil, India, China
Europe: All EU countries plus Switzerland, Norway, Ukraine, Russia
Asia Pacific: Singapore, Hong Kong, Taiwan, South Korea, Indonesia, Thailand, Philippines, Vietnam
Latin America: Mexico, Argentina, Colombia, Chile, Peru
Middle East & Africa: UAE, Saudi Arabia, Israel, South Africa, Egypt, Nigeria
The full list is in the dropdown. If you need a country we don't have, let us know and we'll see what we can do.
Why this matters for QA
International testing is usually an afterthought. Teams build features, test them locally, and assume they work everywhere. Then support tickets roll in from users in specific regions.
With geolocation testing, you can:
- Catch regional bugs before launch - Run your test suite from multiple countries
- Verify compliance implementations - Make sure GDPR banners actually show up in the EU
- Test localization - Confirm prices, currencies, and languages are correct
- Debug region-specific issues - Reproduce exactly what a user in that country sees
This is especially important if you're dealing with e-commerce, fintech, media licensing, or anything with regional restrictions.
Custom plan feature
Geolocation testing is available on Custom plans. We're covering the proxy costs on our end, so this is part of the Custom tier.
If you're on a Pay As You Go plan and need geolocation testing, reach out and we can talk about upgrading. For most teams, the ability to catch international issues before they hit production is worth it.
Getting started
To set a project default:
- Go to Projects in your dashboard
- Edit an existing project or create a new one
- Select a country from the Location dropdown
- Save the project
To override for a specific test plan:
- Go to Test Plans in your dashboard
- Edit the test plan
- Expand Advanced Settings
- Select a different country from the Location dropdown
- Save the test plan
The AI agent will see exactly what a user in that country sees. Screenshots, page content, everything.
Got questions about geolocation testing or need help with a specific regional testing scenario? Contact us and we'll help you set it up.