An AI QA agent helps Saudi and UAE companies check what general test lists ignore: right-to-left layout on every page, Arabic text, numbers and currency, switching between Arabic and English, local mobile and address formats, and VAT in the cart (15% in Saudi Arabia, 5% in the UAE). It tests the purchase journey up to the payment page on staging in test mode, and reruns the check before Ramadan and White Friday. Wallets on real devices and load testing stay with a person and a specialist.
- AI QA agent Saudi Arabia
- how to test an Arabic website
- RTL website testing checklist
- how to test mada payments in test mode
- QA testing for ecommerce in UAE
- how to test my store before Ramadan
Why does testing in Saudi Arabia and the UAE need its own checklist?
Most website test lists were written for an English store whose customer pays by credit card and types a postcode. Your customer in Jeddah or Sharjah browses on a phone, reads Arabic, pays with mada, Apple Pay or installments, and gives an address by district and building. An AI QA agent does what you ask, so if you do not ask for these details, nobody checks them.
Illustration- Language
- Arabic first; English for residents and business
- Device
- Phone before desktop
- Paying in Saudi Arabia
- mada, Apple Pay, STC Pay, Tabby and Tamara
- Paying in the UAE
- Cards, Apple Pay, installments, cash on delivery
- VAT
- A different rate in each country
- Peaks
- Ramadan, the Eids, White Friday, national days
New to the idea? Start with what is an AI QA agent.
Which Arabic and RTL faults should the agent look for?
An Arabic interface breaks in predictable places, and an agent can check many of them in a real browser at phone size. Ask for this list by name:
What an agent does not judge is the wording: natural to a Gulf customer, or a literal translation? That needs an Arabic reader on your team. See Arabic interface mistakes and the Hijri calendar in apps.
How do you test a site in both Arabic and English?
In Dubai, Abu Dhabi and Riyadh many sites serve two audiences. Testing one language and assuming the other matches is the common mistake; a bilingual site is in practice two sites sharing data:
| What you test | How | The common failure |
|---|---|---|
| Every journey in each language | A full run in Arabic, then the same in English | A step works in one language and breaks in the other |
| Switching mid-journey | Change language with a full cart, or on a product page | You land on the home page, or the cart empties |
| Content entered by admins | One product with an Arabic name only, one English only | An empty field, or text in the wrong language |
| Outgoing messages | Order in Arabic and read the email and notice | Arabic interface, English email |
| Invoice and receipt | Check language, numbers and VAT | A one-language invoice for two audiences |
How do you test local payments safely?
Rule one: no real money in an automated run. Payment is tested on staging with the gateway in test mode. When you set up the QA Engineer, under 'what must I never change' write: do not try real payment.
- 1Prepare the staging copy
The gateway's test keys and test cards, and products with known prices.
- 2Let the agent test everything around payment
The cart, VAT and delivery math, the right methods showing, and reaching the payment page.
- 3Complete the test payment yourself
Whether the agent can complete a payment on the gateway's own page depends on your setup. Do not assume; make a test payment by hand for each method.
- 4Check the other end
Did the order turn 'paid' in the admin panel? Did the receipt arrive?
- 5After publishing: a small real amount
Pay a small amount with your own card on live, then refund it.
| Payment method | What the agent checks | What needs a person |
|---|---|---|
| mada, Visa and Mastercard cards | The option shows, the amount, reaching the payment page | Entering the card and the bank's verification code |
| Apple Pay | The button shows in the right place | The payment itself on a real iPhone |
| STC Pay | The option and the mobile field show | The confirmation code on the phone |
| Tabby and Tamara | Installments show with the price and minimum order | The approval journey at the provider |
| Cash on delivery | The full journey to confirmation, and any fee | Usually nothing |
Which local details break forms?
Sign-up and address forms are often copied from foreign templates and frustrate local customers. Ask the agent to try these cases:
| Field | Saudi Arabia | UAE | What to test |
|---|---|---|---|
| Mobile number | Starts with 05, or the 966 code | Starts with 05, or the 971 code | All formats accepted; a short one refused in Arabic |
| Address | District and street, and the short national address | Emirate, area and building; no postcode | The form does not demand a postcode that does not exist |
| VAT | 15% | 5% | Shown in the cart, and the total adds up |
| Working week | Sunday to Thursday | Varies; government runs Monday to Friday | Delivery and booking slots respect working days |
An agent checks that VAT shows in the cart and the numbers add up. Whether your invoices meet e-invoicing rules is a regulatory matter; check the official source, ZATCA in Saudi Arabia or the Federal Tax Authority in the UAE, or your accountant.
How do you prepare for peak seasons?
In the Gulf much of the year's selling lands in a few weeks: Ramadan and the Eids, White Friday in November, National Day and Founding Day in Saudi Arabia, Eid Al Etihad and the Dubai Shopping Festival in the UAE. A bug on those days costs far more than on a normal day.
- 4 weeks beforeA fresh full review
A new plan for the core journeys, in Arabic at phone size. Fix critical and high bugs.
- 3 weeks beforeTest the offers themselves
Season coupons, reduced prices, quantity limits, and offers ending on time.
- 2 weeks beforePayment and load
Test payments with every method. Load testing needs a specialist; it is outside a QA agent's scope.
- 1 week beforeChange freeze
Fixes only, each followed by a full re-check.
- During the seasonA daily quick check
A scheduled run before peak hours, and a named person reading the verdict.
- After the seasonTurn complaints into cases
Every customer complaint becomes a permanent test case for next season.
Season lists: Ramadan checklist for Saudi stores, Ramadan checklist for UAE stores, preparing for White Friday and the Dubai Shopping Festival.
When should scheduled runs happen in the Gulf working week?
Scheduling in the QA Engineer uses Riyadh time and is part of higher plans: every day, every week on a set day, or after every publish. The UAE is one hour ahead.
Pick the one that sounds like you to see the advice.
A daily run at dawn, Riyadh time. A weekly one on Sunday morning, not on Friday when nobody reads the report.
Subtract an hour: 6 am in Dubai is 5 am Riyadh time. For a weekly run, pick your team's first working day.
One daily run before the day starts in both, with cases covering both currencies, VAT rates and mobile formats.
The peak is in the evening and at the weekend. A run before noon every day, Friday and Saturday included.
What belongs in the run is covered in running an AI QA agent every night.
How do you start today in Fanann?
Fanann's QA Engineer has an Arabic interface, and you brief it in Arabic or English. It tests your site or web app in a real browser at phone or desktop size, built in Fanann or elsewhere. It never starts before you approve the plan, changes data only with permission, reports with screenshots and severity, and re-tests after the fix. It is part of the paid plans. It does not test store-installed mobile apps, and does no load testing or security audit.
Test my store with the interface in Arabic at phone size. Confirm every page is right-to-left with no sideways scroll and that error messages are in Arabic. Register with a Saudi mobile number starting with 05, then in the 966 format, and try a short number and Arabic-Indic digits in the field. Add two products to the cart and confirm that 15% VAT is shown and the total is correct. Enter an address in Riyadh by district and street. Continue to the payment page and confirm that mada, Apple Pay, Tabby and Tamara are shown; do not try real payment. Then switch to English with a full cart and confirm it did not empty. You are on the staging copy.
Try it in FanannFor the complete pass, see how to test a website before launch. No site yet? Browse the Saudi market and the UAE market.
Key takeaways
- Arabic interface faults do not show when you test in English; ask the agent explicitly to test in Arabic.
- A bilingual site is tested twice: every journey in each language, then a switch mid-journey.
- Local payments are tested in test mode on staging; never a real payment in an automated run.
- Apple Pay, STC Pay and the bank's verification code need a person with a real phone.
- Before Ramadan and White Friday: a full re-check, a change freeze, and load testing by a specialist.
Frequently asked questions
Can an AI QA agent test Arabic websites?
Can the agent test payment with mada or Apple Pay?
Is payment testing safe on my live store?
When should I start testing my store before Ramadan or White Friday?
Does the agent confirm my invoices meet e-invoicing rules?
Does the QA Engineer work for companies in the UAE?
Ask your AI assistant about this
Copy this prompt into the AI assistant you use, then add the details of your own case.
I am reading this guide: “AI QA agents for Saudi and UAE companies: Arabic, RTL and payments” https://fanann.com/en/blog/ai-qa-agent-saudi-uae-companies/ My question: AI QA agent Saudi Arabia Use that page as a source and explain the answer step by step for my situation, tell me what to check before I start, and cite the page link.