Non-Functional Testing Questions

Test Case ID: QA-I18N-RTL-001
Title: Verify Checkout page localization for RTL language (e.g., Arabic)

Preconditions

• Build deployed to staging; locale files updated.
• Test account exists; cart contains at least one SKU and one discount coupon.
• Browser/system locale set to Arabic (ar) or app locale selection = Arabic.
• Test device supports RTL rendering (desktop/mobile).

Test Steps

1. Open site and switch/apply locale = Arabic.
   • Expected: UI language changes to Arabic; page direction = RTL (html dir="rtl").
2. Navigate to Checkout page.
   • Expected: Layout mirrored: primary column aligns right, progress indicator flows right-to-left, back button position mirrored.
3. Verify UI mirroring for key components:
   • Address form fields: labels appear to the right of inputs; field order preserved but visually mirrored.
   • Payment section: card number, expiry, CVV maintain logical flow; action buttons (Continue/Place Order) aligned right.
4. Verify text translations:
   • Check header, button labels, validation messages, terms text against translation sheet. Mark any missing translations.
   • Expected: All visible strings use Arabic translations.
5. Verify number, currency, and date formats:
   • Prices display currency symbol and formatting per locale (e.g., Arabic-Indic digits if required, decimal and thousands separators).
   • Order summary totals, tax, shipping use correct format.
6. Verify fallback behavior:
   • Intentionally remove a translation key (or use staging with a missing key).
   • Expected: Fallback to default language (English) or show translation key based on spec; no UI break; placeholder flagged for devs.
7. Accessibility & RTL-specific checks:
   • Ensure icons (chevrons) flipped, focus order logical, screen reader reads Arabic text correctly.
8. Finalize order and verify confirmation page remains RTL and formats persist.

Pass Criteria / Expected Results

• Page direction = RTL and visual mirroring consistent across components.
• All visible strings translated; missing translations follow specified fallback policy.
• Currency, number, and date formats match locale conventions.
• No layout overlap, truncated text, or functionality regressions introduced by RTL.
• Issues logged with screenshots, DOM snippets (dir attr), and translation keys for failures.