Skip to main content

What are advanced configurations?

Advanced Configurations let you set the run location, network conditions, headers, and HTTPS credentials for a test — useful for A/B testing, header modifications and internal logic validation. Open Advanced in the test editor to configure the test execution environment.

Configuration options

Test run location

Test run locations are an add-on that Spur enables for your Application. Open Test Run Location in the test’s Advanced section. This replaces the former Locale control. Search for a country, city, language, or timezone, then select a location enabled for your Application. The selected profile shows its IP origin, language, clock, and coordinates. Selecting a location also selects that profile’s language. Select No location to clear the test’s selected location. Locations that your Application cannot use appear grayed out with Not enabled. If none are enabled, the control says so. Contact Spur to request the locations you need. Native tests show this location control. The other settings below apply to web tests.

Network throttling

Simulate different network conditions including packet loss. Use for testing performance on slower connections and validating loading states.

Available options:

  • None (default)
  • Fast 4G
  • Slow 4G
  • 3G
  • Offline
  • Custom

Packet Loss options:

  • None - 0% (default)
  • Low - 2%
  • High - 5%
  • Extreme - 10%
Network Throttling
Use cases:
  • Testing application behavior on mobile networks
  • Validating loading states and timeouts

Capture HAR

Turn on Capture HAR to record the run’s network traffic as a downloadable HAR file. Capture HAR is available for web tests only. To learn how to download the file, see Capture a HAR file.

Headers

Add custom HTTP headers to requests. Headers set to Apply to all tests and headers from the test’s suite appear first, followed by any additional headers you add.
  • All tests headers are sent on every test run. The chip is dimmed when the test or its suite selects its own headers, because that selection takes precedence.
  • Suite headers come from the suite’s Default Environment Properties. Click the remove icon on a suite header to remove it for this test only. The suite’s remaining headers become this test’s own selection.
  • A header with no value in the environment you’re previewing shows No value in this environment — not sent here.
Headers
Use cases:
  • Adding authentication tokens
  • Setting custom API headers
  • A/B testing with custom headers

Route overrides

Route overrides intercept and modify network requests during test execution, so you can mock API responses, redirect requests, or inject test data. Under Route Overrides, select from the route overrides set up for your Environment. You can’t create a route override on the Environments page. Contact Spur to add one.
Mock Network Call
Use cases:
  • Mock API endpoints to control test conditions: Override backend responses to ensure consistent test behavior. For example, mock a checkout endpoint to return a successful order confirmation, allowing you to test post-purchase flows without processing real transactions.
    Mock Network Call

HTTPS credentials

Configure HTTP basic authentication credentials for tests that require authentication. Credentials set to Apply to all tests appear with an All tests chip. The chip is dimmed when the test or its suite selects its own credential. Only one credential can be selected per test.
HTTPS Credentials
Use cases:
  • Testing password-protected staging environments: Authenticate automatically to staging sites that require HTTP basic auth before the Spur agent begins test execution
    HTTPS Credentials
  • Accessing internal development servers: Bypass authentication prompts on internal servers during automated testing without exposing credentials in test scripts.
  • Validating authentication flows: Test that proper authentication is required and that invalid credentials are rejected as expected.