What to test in Iraq
Start with a local question. Keep the network, language, and delivery settings separate so the result tells you something useful.
Keep Arabic and Kurdish journeys distinct
For Iraq localization, test Arabic and the Kurdish version your application supports as separate paths. Record script, language, and query text. A country-level exit cannot determine the interface preference, and a translated homepage cannot validate the rest of the customer journey.
Compare Baghdad and Erbil address scenarios
Use supported Iraq test addresses in Baghdad and Erbil to inspect city selection, contact fields, and delivery options. Preserve the chosen values through the final summary. This tests the application's address logic without implying selectable city-level proxy exits.
Retain the original dinar price string
For Iraq offer comparisons, store the currency code and raw amount before normalizing digits or separators. Match product package and seller, then compare equivalent delivery conditions. A successful connection does not validate a price parser or make different regional listings interchangeable.