ZTABS provides QA testing for Saudi digital projects — Arabic RTL interface testing ensuring flawless bidirectional layouts, government platform validation for Vision 2030 digital services, and mobile-first testing for Saudi Arabia's 98% smartphone penetration market.
Saudi Arabia's digital transformation under Vision 2030 is producing software at unprecedented scale — government super apps (Tawakkalna, Absher, Sehhaty), banking applications (all Saudi banks now offer digital banking), fintech platforms (STC Pay, stc bank, Tamara BNPL), e-commerce (Noon, Jarir, Extra), and enterprise platforms for every government entity. The quality bar is high and rising. Saudi users have high expectations — they use global apps (Instagram, WhatsApp, Uber) daily and expect local apps to match that quality. When a government service is slow, citizens complain on Twitter (Saudi Arabia has one of the world's highest per-capita Twitter usage rates). When a banking app crashes, the customer switches to a competitor (Saudi banking is competitive — 30+ licensed banks). Saudi QA testing has unique requirements that generic QA approaches miss. Arabic RTL (right-to-left) testing is the most critical and most commonly failed. RTL is not simply "flip the layout" — it requires: mirrored navigation (menus, breadcrumbs, and progress indicators must flow right-to-left), bidirectional text handling (Arabic text with embedded English words, numbers, or brand names must render correctly — a sentence like "أكمل الدفع عبر Apple Pay" must show Arabic RTL with "Apple Pay" remaining LTR), numeral handling (Arabic-Indic numerals ١٢٣ vs. Western Arabic numerals 123 — Saudi users expect either to work, and the application must handle both in forms, displays, and calculations), and date format (Saudi Arabia uses Hijri calendar alongside Gregorian — applications must display and accept both, with correct conversion). Beyond RTL, Saudi QA requires: mobile-first testing (Saudi smartphone penetration is 98% — the mobile experience is the primary experience, not a secondary consideration), performance testing for Saudi infrastructure (Saudi 5G coverage is extensive in cities but mobile data performance varies — applications must work well on both high-speed 5G and slower connections in rural areas), integration testing with Saudi government systems (Nafath for authentication, ZATCA for e-invoicing, Absher for government services — each integration must be tested thoroughly), and Ramadan/Eid load testing (Saudi applications experience extreme traffic spikes during Ramadan and Eid — e-commerce traffic can spike 5-10x, government services see surges at end of fasting hours).
Riyadh QA demand spans government digital services, banking, e-commerce, and enterprise applications. Government platforms: Saudi government entities deliver citizen services digitally. QA requirements: Arabic-first usability testing (government services must work flawlessly in Arabic — including: form validation with Arabic input, error messages in Arabic, and help text in Arabic), accessibility testing (Saudi government platforms must be accessible to users with disabilities — Vision 2030 includes disability inclusion goals), Nafath authentication testing (every government service requiring identity verification must test: Nafath redirect flow, session handling, timeout scenarios, and fallback paths when Nafath is unavailable), and cross-device testing (Saudi citizens access government services from: iPhones (dominant in Saudi market), Android devices (Samsung, Huawei), tablets, and desktop browsers — each must work correctly). Banking and fintech: Saudi banks and fintech companies need: payment flow testing (SADAD for bill payments, mada for card payments, STC Pay, Apple Pay — each payment method requires separate testing with success, failure, timeout, and reversal scenarios), SAMA compliance testing (Saudi Arabian Monetary Authority regulations require specific security controls — testing that: transaction limits are enforced, SCA is implemented correctly, and fraud detection triggers appropriately), Arabic number input testing (Saudi users may enter amounts using Arabic-Indic numerals or Western Arabic numerals — the application must accept both and process correctly), and biometric testing (Saudi banking apps use Face ID and fingerprint authentication — testing biometric flows on multiple device types). E-commerce: Saudi e-commerce platforms need: Arabic product search testing (Arabic morphology makes search challenging — searching for "حذاء" (shoe) should find "أحذية" (shoes) and "حذاء رياضي" (sports shoe) — testing that Arabic search handles morphological variants), checkout flow testing (cart → address → payment → confirmation — tested with: Arabic addresses, multiple payment methods, COD, BNPL options like Tamara and Tabby, and ZATCA-compliant invoice generation), delivery address testing (Saudi addresses can be: traditional (district, street name), National Address format (short code), or GPS pin — the application must handle all formats), and seasonal load testing (Ramadan shopping season, White Friday, Saudi National Day — testing application performance under 5-10x normal traffic). Enterprise applications: Saudi enterprise software needs: Arabic ERP testing (SAP Arabic localization testing — verifying that Arabic text renders correctly in reports, forms, and dashboards, that Hijri dates calculate correctly, and that Arabic search works in master data), multi-language testing (many Saudi enterprise applications serve Arabic and English users — testing that language switching works correctly throughout the application, that no hardcoded strings appear, and that layouts adapt correctly), and integration testing (testing integrations with: ZATCA for e-invoicing, GOSI for social insurance, MOL for labor management, and Muqeem for immigration — each government API has specific requirements and error handling patterns).
Our Riyadh QA practice specializes in Arabic-first testing methodologies that catch the RTL, localization, and cultural issues that generic QA misses. Arabic RTL testing framework: (1) We test every aspect of RTL rendering: layout mirroring (navigation menus align right, content flows right-to-left, progress bars fill right-to-left, sliders operate right-to-left), bidirectional text (BiDi testing — sentences containing Arabic and English render correctly with proper directional isolation, parentheses and brackets face the correct direction, phone numbers and email addresses remain LTR within RTL context), form testing (Arabic input in text fields — testing: character display during typing, cursor position, text selection, copy/paste behavior, and form validation with Arabic input), numeral testing (Arabic-Indic numerals ١٢٣ and Western Arabic numerals 123 both accepted in: amount fields, phone number fields, date fields, and search queries — calculated correctly regardless of numeral system), and calendar testing (Hijri and Gregorian dates: display correctly, convert accurately, calculate age and duration correctly, and handle leap years in both calendar systems). Mobile testing: (1) Saudi Arabia is mobile-first — 98% smartphone penetration with iPhone dominant in the premium segment and Samsung dominant in the mid-range. We test: iOS priority (iPhone 13, 14, 15 series — covering the devices 70%+ of Saudi premium users carry), Android coverage (Samsung Galaxy S and A series, Huawei — the primary Android devices in Saudi market), screen size adaptation (from iPhone SE to iPad Pro — the application must work across the full range without layout breaks), and network condition testing (testing on: 5G (urban Riyadh), 4G (suburban), and 3G (rural — still common in some areas) — ensuring the application remains usable on slower connections). Government integration testing: (1) Saudi government API integrations require specific testing: Nafath testing (testing the complete authentication flow: app redirect → Nafath verification → callback with identity data, plus: timeout handling, session management, error states, and the fallback flow when the user does not have Nafath installed), ZATCA e-invoicing testing (testing invoice generation, submission, and validation against ZATCA standards — including: XML schema compliance, QR code generation, and cryptographic signing), and National Address testing (validating address input and lookup against Saudi Post's National Address system — including: short code validation, address standardization, and geocoding). Performance and load testing: (1) Saudi applications face extreme seasonal patterns: Ramadan load testing (simulating the traffic surge that occurs daily after Iftar — when millions of Saudis simultaneously access: e-commerce, food delivery, entertainment, and government services), Eid spike testing (testing capacity for the Eid shopping and travel booking surge — typically 5-8x normal traffic for 3-5 days), and month-end government services (testing for the traffic spike when salary payments trigger: bill payments, SADAD transactions, and financial service usage).
Government / Public Sector
A Saudi government entity launching a citizen services super app (combining 15 government services into one application) had completed development but had no structured QA process. The app was built by a large system integrator — 200,000+ lines of code across iOS, Android, and backend services. The problems: (1) Arabic rendering issues: internal review found 340+ RTL layout issues (text overlapping, misaligned icons, broken bidirectional text in forms). The development team had tested primarily in English and added Arabic translations late. (2) No automated testing: the system integrator delivered the application with zero automated tests. Each release required 3 weeks of manual testing by a 12-person team — testing 15 service modules across 2 platforms (iOS and Android) with Arabic and English interfaces. (3) Nafath integration instability: the Nafath authentication flow failed intermittently — users reported being "stuck" after Nafath verification, with the app not receiving the callback. The bug was intermittent and not reproducible with manual testing. (4) Performance concerns: the app was expected to serve 5 million users within 6 months of launch. No load testing had been conducted. The backend was designed for 10,000 concurrent users — nobody knew if this was sufficient. (5) Accessibility gaps: the app was mandated to meet accessibility standards under Saudi disability inclusion regulations. An initial accessibility scan found 180+ issues (missing aria labels, low color contrast, non-functional keyboard navigation).
We implemented QA over 8 weeks (pre-launch deadline): (1) Arabic RTL audit and fix verification: systematic audit of all 340+ RTL issues — categorized by severity: Critical (35 issues): text truncation preventing users from reading content, form inputs not accepting Arabic text correctly, payment amounts displaying incorrectly with Arabic-Indic numerals. Major (120 issues): icon alignment, directional indicators pointing wrong way, BiDi text breaking in specific contexts. Minor (185 issues): spacing inconsistencies, font rendering variations, non-critical visual alignment. We worked with the development team to prioritize fixes — critical issues blocked launch, major issues fixed within 2 weeks post-launch, minor issues in the first maintenance release. Automated RTL regression tests: 85 Playwright tests specifically validating RTL rendering — running in CI to prevent RTL issues from recurring. (2) Automated test suite: 600 automated tests created in 6 weeks: 250 unit tests for backend services (covering: eligibility calculations for each of the 15 government services, date conversion logic (Hijri/Gregorian), and Arabic text processing functions), 200 API integration tests (testing each of the 15 service APIs: request validation, response format, error handling, timeout behavior, and authentication), and 150 E2E tests using Playwright (75 for iOS, 75 for Android — covering the critical journey for each of the 15 services: service discovery → authentication → form completion → submission → status tracking, tested in both Arabic and English). (3) Nafath integration testing: created a dedicated Nafath test harness simulating: successful authentication (happy path — user verifies in Nafath, callback received, session established), timeout (user does not respond to Nafath within 120 seconds — the app must handle gracefully, not hang), network failure during callback (the Nafath verification succeeds but the callback fails due to network — the app must retry or provide a manual verification option), and concurrent sessions (user has multiple tabs/devices attempting Nafath simultaneously — the app must handle without creating duplicate sessions). The testing identified the root cause of the intermittent failure: a race condition in the callback handler when the user switched apps during Nafath verification — the app lost its foreground state listener and missed the callback. Fixed and verified with automated tests. (4) Performance testing: k6 load tests simulating Saudi usage patterns: normal weekday load (50,000 concurrent users — baseline validation), Ramadan evening spike (200,000 concurrent users — simulating the post-Iftar surge), and launch day projection (500,000 concurrent users — the expected first-day adoption). Results: the backend handled 50,000 concurrent users with acceptable response times (< 500ms p95). At 200,000 concurrent users, response times degraded to 3+ seconds — unacceptable. Root cause: database connection pool exhaustion — fixed by implementing connection pooling and caching for frequently-accessed reference data. After optimization: 500,000 concurrent users with < 800ms p95 response time. (5) Accessibility remediation: the 180 accessibility issues addressed in priority order: 45 critical (screen reader users could not navigate core services — aria labels added, focus management implemented, form labels corrected), 80 major (color contrast, touch target sizes, error announcement — fixed in the first release), and 55 minor (heading hierarchy, landmark regions — fixed in the maintenance release). Accessibility testing integrated into CI/CD — axe-core scans on every build.
Launch: the app launched on schedule. Day 1: 180,000 downloads. Week 1: 620,000 downloads. Month 1: 2.1 million active users. No critical issues in the first 30 days — the first government app launch in the entity's history without a post-launch emergency fix. Arabic quality: RTL issues in production: 3 minor visual issues reported in the first month (vs. 340+ found pre-launch). User feedback specifically praised the Arabic interface quality — "finally a government app that feels designed for Arabic, not translated." Nafath reliability: authentication success rate: 99.2% (vs. approximately 85% before the race condition fix). The remaining 0.8% failures are attributable to: user-side issues (Nafath app not installed, phone not connected), not application bugs. Performance: the app handled the Ramadan evening traffic spike (peak: 280,000 concurrent users) without degradation. Response times remained under 1 second throughout. No availability incidents during the first 3 months. Accessibility: Saudi accessibility advocacy group rated the app as one of the most accessible government applications in the Kingdom — contributing to the entity's accessibility compliance for disability inclusion reporting. Ongoing QA: the automated test suite (600 tests) runs on every code change. Release cycle reduced from 3 weeks (manual testing) to 3 days (automated testing + targeted manual exploratory testing). The entity releases updates bi-weekly instead of quarterly. Project cost: SAR 480,000. Value: on-time launch (avoiding the SAR 2M+ monthly delay cost estimated by the entity), user trust preservation (2.1 million users acquired without quality-driven churn), and ongoing release velocity improvement.
Automated unit, integration, and E2E tests with Jest, Cypress, Playwright, and more.
Exploratory testing, regression, and UAT to validate real-world usage and edge cases.
Load, stress, and scalability tests to ensure apps perform under real traffic.
Tests integrated into your pipeline for continuous feedback on every change.
Test plans, coverage analysis, and risk-based prioritization for efficient QA.
Riyadh QA options include: global testing companies (Accenture, Cognizant, TCS — large-scale testing operations but at SAR 800-1,200/day per tester, with limited Arabic RTL specialization), regional QA companies (emerging Saudi QA companies — growing capability but limited track record), the system integrator's QA team (the same company that built the application also testing it — inherent conflict of interest and often the same blind spots), offshore QA teams (Indian testing companies — cost-effective but with no Arabic testing capability, no understanding of Saudi government integration requirements, and no experience with Nafath/ZATCA), and independent testers (freelance QA professionals — Saudi freelance QA market is small but growing). The gap: global companies provide testing volume without Arabic specialization. The system integrator tests its own work without independence. Offshore teams cannot test Arabic interfaces or Saudi integrations. ZTABS provides independent QA with Arabic-first testing methodology, Saudi government integration expertise, and automated testing that becomes a permanent part of the development pipeline.
QA testing in Riyadh ranges from SAR 60,000 for a focused test automation implementation to SAR 600,000+ for comprehensive QA for large government platforms. Government super app QA (as in the case study): SAR 480,000. Arabic RTL testing audit: SAR 30,000-60,000. Test automation implementation (300-500 tests): SAR 80,000-150,000. Performance/load testing: SAR 40,000-80,000. Accessibility audit and remediation: SAR 30,000-60,000.
Verified reviews from real client engagements — sourced from our public testimonial archive and Clutch profile.
My experience is throughout positive. Communication, service, the short response times and the flawless execution of a challenging topic was absolutely great. ZTABS is definitely my first choice again.
Christian Neff
Bank Software Advisory · Bank Software Advisory
Fintech
Fantastic Agency! I couldn't fault them even if I tried. They always go above and beyond to meet your expectations and always produces quality work. Thank you ZTABS.
Stephanie Kal
CEO · Beauty Finder Australia
Marketplace
It has been great working with ZTABS. They bounce off the ideas along the way. Amazing Experience.
Joel Rowe
CEO · Drill Quoter
Marketplace
We don't just contract — we ship and operate our own software. 17 products in production.
Common questions about qa & testing for Riyadh businesses
This is our primary specialization for Saudi QA. We test: layout mirroring, bidirectional text rendering, Arabic-Indic numeral handling, Hijri calendar functionality, Arabic form input and validation, and Arabic search with morphological matching. Our automated RTL test suite catches issues that non-Arabic-speaking QA teams consistently miss.
ZTABS is a remote-first qa & testing agency serving Houston businesses — including test automation, manual qa, performance testing. We work with Energy & Oil/Gas, Healthcare & Biotech, Aerospace & Defense companies in Houston, TX via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
QA & Testing in New York, NYZTABS is a remote-first qa & testing agency serving New York businesses — including test automation, manual qa, performance testing. We work with Finance & Fintech, Media & Advertising, Fashion & Retail companies in New York, NY via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
QA & Testing in Los Angeles, CAZTABS is a remote-first qa & testing agency serving Los Angeles businesses — including test automation, manual qa, performance testing. We work with Entertainment & Media, E-commerce & DTC Brands, Gaming & AR/VR companies in Los Angeles, CA via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Development in Riyadh, Saudi ArabiaZTABS is a remote-first web development agency serving Riyadh businesses — including full-stack development, progressive web apps, api development. We work with GovTech, FinTech, Energy Tech companies in Riyadh, Saudi Arabia via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
Web Design in Riyadh, Saudi ArabiaZTABS is a remote-first web design agency serving Riyadh businesses — including ui/ux design, responsive design, custom interfaces. We work with GovTech, FinTech, Energy Tech companies in Riyadh, Saudi Arabia via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
AI Development in Riyadh, Saudi ArabiaZTABS is a remote-first AI development agency serving Riyadh businesses — including llm integration & fine-tuning, ai agents & automation, rag & knowledge systems. We work with GovTech, FinTech, Energy Tech companies in Riyadh, Saudi Arabia via timezone-aligned engineers and async workflows; we do not have a local office, and we are explicit about that with every client.
QA & TestingLearn more about our qa & testing services nationwide.
Partner with ZTABS for expert qa & testing in Riyadh. Get a free consultation today.
