Drivepass AUTOMOTIVE ABSOLUTE.

User Acceptance Testing (UAT)

Arabic Localisation — Analytics & Reports

Drivepass Ignition · Admin / National Sales Manager surfaces
TesterIbrahim Jamal Al Lail (in-house — first pass)
BuildBranch feat/i18n-analytics-reports · commit 1b9c89e
EnvironmentVercel preview (link in your email) — NOT production
Loginmohamed@demo.com (national_sales_manager)
Important — what is and isn't in this build
• Covers the Analytics dashboards, leads list pages, CSV exports, and ONE PDF report (CRM Funnel) as a proof.
• Other PDF reports currently download as Arabic-style images but with ENGLISH text inside — expected at this stage, NOT a failure. Only test the CRM Funnel PDF for Arabic (Section 5).
• Vehicle model names (Montero, Outlander, etc.) stay in English on purpose — brand names, not an error.
• Empty values shown as a dash ( — ) are intentional.
How to use: Switch the app to Arabic before each section. Work through each case, choose Pass / Fail / N/A, and add notes (especially for any FAIL — say what and where). For CSV and PDF you must OPEN the downloaded file, not just click the button. When done, hit Submit at the bottom — results come straight to the team.

Section 1 — Analytics tables (values in Arabic)

Switch the app to Arabic. Go to the Analytics area as the national sales manager. For each table, check that the VALUES (not just the column headers) appear in Arabic.

1.1Not Qualified Reasons table — values under the “Reason” (السبب) column
Expected: Each reason shows in Arabic, not English. Empty reason shows as “—”.
1.2Lead Status Breakdown table — status and sub-status values
Expected: Status and sub-status values in Arabic (headers were already Arabic).
1.3Active Pipeline table — status and sub-status columns
Expected: Both columns show Arabic values; empty cells show “—”.
1.4Closed Lost Reasons table
Expected: Reason values in Arabic; “—” where no reason exists.
1.5Lead Source Performance table
Expected: Lead source values in Arabic.
1.6Request Type table
Expected: Request type values in Arabic.
1.7Branch Performance page — status/sub-status pivot AND Active Leads table
Expected: All status and sub-status values in Arabic across both tables.
1.8Cleanup tab — Dormant Leads and Recently Created tables
Expected: Status values in Arabic in both tables.
1.9Model Interest table
Expected: Model names remain in English (correct — brand names). Everything else around them is Arabic.

Section 2 — Leads list pages (values in Arabic)

Still in Arabic mode, open each leads list page and check the status / sub-status / reason values in the rows.

2.1All Leads page — status badge and sub-status column
Expected: Status and sub-status in Arabic; empty sub-status shows “—”.
2.2Pending Leads page — status column
Expected: Status values in Arabic.
2.3Closed Leads page — sub-status reason column
Expected: Reason values in Arabic; “—” where empty.
2.4Any leads table — column header alignment
Expected: Headers align to the RIGHT (RTL), not the left.

Section 3 — Charts (labels in Arabic)

In Arabic mode, switch the relevant analytics sections to their CHART view and check the labels. NOTE: chart legend position / bar direction (RTL mirroring) is a separate later task — only check that the LABEL TEXT is Arabic.

3.1Lead Source chart (doughnut + bar) — category labels
Expected: Lead source labels in Arabic.
3.2Not Qualified Reasons chart (pie)
Expected: Reason labels in Arabic; empty shows “—”.
3.3Closed Lost Reasons chart (pie)
Expected: Reason labels in Arabic.
3.4Lead Source bar chart — dataset labels (qualification %, conversion %)
Expected: Dataset labels in Arabic.
3.5Model Interest chart — category labels
Expected: Model names stay English (correct). Other labels Arabic.
3.6Chart legends / tooltips text
Expected: Translated label text inside legends and tooltips reads in Arabic.

Section 4 — CSV exports (open the file in Excel on Windows)

The previous problem was Arabic showing as broken symbols (mojibake) in Excel on Windows. For each export: switch to Arabic, click the CSV/Export button, then OPEN the file in Microsoft Excel on Windows.

4.1Any Analytics CSV (e.g. CRM Funnel) opened in Excel on Windows
Expected: Arabic displays correctly — NOT broken symbols like اب.
4.2Same CSV — column headers
Expected: Headers in Arabic.
4.3Same CSV — status / sub-status / reason values
Expected: Values in Arabic.
4.4All Leads page — CSV export
Expected: Opens in Excel with Arabic intact; headers and values Arabic.
4.5Closed Leads page — CSV export
Expected: Opens in Excel with Arabic intact; reason values Arabic.
4.6All Leads — export a very large result (filter with many leads)
Expected: If capped, a visible AMBER warning banner appears saying the file shows only the first rows (only over ~10,000 rows).
4.7Optional — open the same CSV in Google Sheets
Expected: Arabic displays correctly there too (confirms the fix).

Section 5 — PDF export (CRM Funnel only — the proof)

The key test of the new Arabic PDF method. ONLY the CRM Funnel report is wired for Arabic content in this build. Switch to Arabic, go to Analytics → CRM Funnel, click the PDF button, and OPEN the downloaded PDF. (Other PDF reports will show English text inside for now — that is expected, do not fail them here.)

5.1Arabic letters are CONNECTED (joined into words)
Expected: Letters join naturally — NOT separated into single standalone letters.
5.2Text reads RIGHT-TO-LEFT correctly
Expected: Words read in the correct direction — not reversed / backwards.
5.3Numbers are still readable
Expected: Numbers display left-to-right and correctly (normal for numbers).
5.4Text is SHARP, not blurry
Expected: Text is crisp and clearly legible, not fuzzy or pixelated.
5.5Report title and stage names are in ARABIC
Expected: Title and funnel stage names in Arabic, not English.
5.6Multi-page (if long) — no row cut in half at a page break
Expected: Rows not clipped across the page break (if slightly clipped, note it — known item).
5.7Switch to ENGLISH, export same CRM Funnel PDF
Expected: English PDF still works exactly as before (no breakage).

Section 6 — Arabic wording review

You are the Arabic authority. Beyond translated/not, flag any wording that is technically Arabic but reads wrong, awkward, or is the wrong term for our Mitsubishi workflow. Use the notes fields above to record specifics, and the box below for an overall summary.

6.1Any status / sub-status / reason value with WRONG or awkward Arabic
Expected: Use notes: English value, what it shows, what it should say.
6.2CSV truncation warning banner wording (if you triggered 4.6)
Expected: Confirm Arabic reads naturally; suggest better wording if not.
6.3Any report title or column header with awkward Arabic
Expected: Note the report and suggested correction.

Overall sign-off

Summary of issues (reference the test number for each):