1. Define what you want to observe
Choose a precise question: does the displayed currency change, is the catalog different, does the cart remain consistent? Set the authorized scope, URLs, time window and number of attempts. Avoid vague objectives such as checking that the proxy works everywhere.
2. Prepare the browser context
Define the exit country, language, time zone, device and cookie state. To compare two countries, keep the other settings unchanged wherever possible. Document every setting you change, including any market preference on the website.
3. Check the connection before the workflow
Check the delivered access with a short request and record the exit IP. Then check the detected country. If these steps fail, resolve them before drawing conclusions about the catalog or campaign under review.
4. Measure, then 5. keep the evidence
Run the scenario with an attempt limit and reasonable timeouts. Record the expected result, actual result, UTC time and redacted errors. A screenshot can supplement the record but does not replace the settings. Repeat under comparable conditions before interpreting a one-off difference as a trend.
Frequently asked questions
Should I always clear cookies?
It depends on the scenario. A first visit and a returning customer are different tests. What matters is keeping this state explicit and consistent throughout the comparison.
What measurement is enough to call a test successful?
Both the technical response and the task outcome must match the scenario. A 200 status alone does not guarantee the right country, product or currency.