Build and Run Tests

Browser Location

View as Markdown

Choose where your web tests’ browser traffic exits from. The location applies to all traffic the test browser sends — page loads, API calls the page makes, and sign-in flows.

LocationExit IPsUse it for
US (Static IP) — defaultFixed set of US IP addressesApps that restrict access by IP, or that should see US visitors
EuropeRotating residential IPs in GermanyApps that should see EU visitors — EU locale, GDPR consent banners, region-gated content

Allowlist TesterArmy’s IPs

With US (Static IP) — the default — every run exits from a small, fixed set of IP addresses, so you can allowlist TesterArmy in your firewall, WAF, or VPN.

  1. Open the project.
  2. Go to Settings.
  3. Find Browser Location — the exit IPs are listed under the selector with a copy button.
  4. Add those IPs to your allowlist.

The Europe location uses rotating residential IPs and cannot be allowlisted; if your app restricts access by IP, keep the US location.

Change the Project Default

  1. Open the project.
  2. Go to Settings.
  3. Under Browser Location, pick US (Static IP) or Europe.
  4. Save.

The setting applies to all future web runs in the project — manual runs, group and scheduled runs, PR testing, and API-triggered runs.

Override per Test

Individual tests can use a different location than the project:

  1. Open the test.
  2. Open Test settings.
  3. Select a Browser Location: Project Default, Europe, or US (Static IP).
  4. Save the test.

Writing Test Steps

The agent knows the browser’s location, so steps such as “verify the price shows in euros” behave as a real visitor from that region. Do not add steps that try to change the location from inside a test — configure it in settings instead.