Test case library · Mobile platform
This flow covers apps offered in Hindi and other Indian languages: the language picker, switching mid-session, how Indian scripts render, and how numbers, dates, input, search and voice behave. Most bugs only show up with real text: conjuncts that break apart, vowel signs clipped by fixed-height boxes, long Tamil or Malayalam labels that overflow buttons, and older phones that show empty boxes. Errors and notifications left in English undo the effort for users who chose their language.
From the reviews. Hindi storefront reviews were more critical than English ones: 49.8% negative against 32.2%, with 14.2% describing a malfunction against 12.0%.
Expected: Each language appears in its own script, such as हिन्दी, தமிழ் and বাংলা, so users can find theirs without reading English. After choosing Hindi, every screen in the flow is in Hindi apart from brand and product names.
Expected: The app switches to Tamil without logging out or emptying the cart. Screens reached with Back also show Tamil, not a mix of languages.
Expected: The app opens in Marathi both times, with no English splash or home screen shown first.
Expected: All three searches return the same main products, or the app suggests the matching term. The Hindi search does not show an empty results page when the English one has matches.
Expected: The spoken words appear as editable Hindi text, and search results match the item. If speech is not understood, the app asks the user to try again in Hindi.
Why a real phone: Needs a real microphone, real speech and everyday background noise
Expected: Both notifications are in Hindi, the app's language, not the phone's. Vowel signs are not clipped and the expanded text is shown in full.
Why a real phone: Notification shade fonts and layouts come from the phone maker's Android skin
Expected: Each message is in Hindi, including those that come from the server. None appears only in English or as an error code.
Expected: The app either converts the digits, showing ₹500 and accepting the OTP, or asks for 0–9 digits with a clear message. It never reads the amount as zero or a different value.
Expected: The text appears exactly as typed on every screen and in the invoice. No question marks, empty boxes or jumbled letters appear.
Expected: A message in Hindi explains that this name must be typed in English letters, exactly as on the document. It does not show a generic Invalid input error.
Expected: Every status and label matches the glossary. A failed payment is never shown with a word meaning success or pending, and debit is never confused with credit.
Expected: Conjuncts show as joined letters, with no visible halant (्) or dotted circle. Vowel signs and the र mark in words like पूर्ण sit on the correct letters.
Expected: The tops and bottoms of letters are fully visible inside each box. Text cut with an ellipsis ends after a complete letter, with no broken conjunct or stray vowel sign.
Expected: Labels wrap or shrink to fit, and key buttons such as Pay and Confirm show their full label. No text overlaps icons or runs off the screen.
Expected: Amounts show Indian grouping such as ₹1,00,000 and ₹1,00,00,000 in every language and region setting. The typed amount is grouped the same way, with the ₹ symbol next to it.
Expected: Dates are in day-month-year order with Hindi or numeric months, never month first, and times are in IST. Relative times read correctly for one and many, such as 1 घंटा पहले and 3 घंटे पहले.
Expected: The text is shown exactly as typed, with Roman and Hindi words in the same order. The emoji and the number 5 are kept.
Expected: Both searches return the same results, even though keyboards can encode the dotted letter differently.
Expected: The OTP fills in on its own, as it does when the SMS is in English. If auto-fill fails, the screen explains in Hindi how to type it in.
Why a real phone: Needs real SMS delivery from the carrier to test auto-fill
Expected: All screens after the web page stay in Hindi. No screen switches back to the phone's language.
Expected: The result screen and every later screen are in Hindi. The app does not switch to the phone's language or restart on return.
Why a real phone: Needs a real UPI app handover and return on a physical phone
Expected: The app switches using text already on the phone, or says the language needs internet and stays in English. No screen shows blank labels or raw text keys such as label_pay_now.
Expected: The app does not crash and the typed details are still there. The app follows the new phone language or keeps its own setting, as designed.
Why a real phone: Budget phones often kill the app in the background while the system language changes
Expected: Screens do not show English first and switch to Bengali after a delay. Loading messages are in Bengali too.
Expected: All text shows as readable letters, with no empty boxes or question marks. Conjuncts join the same way as on a newer phone.
Why a real phone: Older phones and phone makers' system fonts lack or change some Indic glyphs
Expected: Text in both languages stays readable, with no empty boxes, overlapping lines or clipped vowel signs. Layouts still fit on screen.
Why a real phone: Font style and theme settings are phone maker features not found on emulators
Expected: Each text field accepts the characters, and nothing typed is lost or reordered when layouts switch. Phone number and OTP fields open the number keypad, not the Hindi layout.
Why a real phone: Phone makers' default keyboards and their Hindi layouts differ by brand
Expected: The app opens in Hindi on both phones, and its own language setting shows Hindi. Changing the language inside the app does not leave the two settings out of step.
Expected: Labels are readable and, if cut short, end after a complete letter. Each shortcut opens the right screen in Hindi.
Why a real phone: Home screen label truncation differs across phone makers' launchers
Expected: The app lock screen appears before any account data. The screen behind it is not visible while the app reloads in the new language.
Expected: Warnings and consent text are fully in Tamil, with nothing important left only in English. A fluent reader confirms the meaning matches the English text.
Expected: The amount, payee name and masked account number match what was entered, with digits and decimals unchanged. Nothing on the screen is cut off or reordered by the translation.
Expected: Layouts run right to left, with text right-aligned and back arrows and progress steps mirrored. Icons such as a clock or a tick are not flipped.
Expected: Numbers, IDs and English words read left to right in the correct order inside the right-to-left text. The saved address shows in the same order as typed.
Expected: Labels, buttons and images are read in Hindi, not as English labels or letter by letter. No control is announced only as Button.
Expected: Every screen scrolls to show all content, and no button is hidden, cut off or overlapping. Key actions such as Pay can always be reached.
They fit the Standard package: 10 × 45-minute sessions on 4 phones or browsers of your choice, up to ~50 cases, ₹18,999 + GST ($249), verified report in 3 business days. The 10 P1 cases alone fit Starter (₹9,999 + GST).
Download the CSV, pick the package at checkout and upload the file with your build. Testers run them on their own phones, on Jio, Airtel and Vi.
Use real Hindi words with conjuncts and vowel signs above and below the letters, such as क्षमा, श्रेणी, कृपया and पूर्ण, and check them in buttons, inputs and lists. Look for visible halant marks, dotted circles, clipped tops or bottoms, and conjuncts broken by an ellipsis. Repeat on an older budget Android phone and on a phone with a custom system font, where rendering most often differs.
Many Hindi keyboards can type Devanagari digits such as १२३ instead of 0–9. Amount, OTP and phone fields should open the number keypad, and if native digits still arrive, either convert them to the same value or ask for 0–9 with a clear message. Test this on payment and OTP screens, where a misread digit can change an amount or block login.
Switch the app to Urdu and check that layouts, text alignment, back arrows and progress steps are mirrored, while icons such as a clock stay unflipped. Then check mixed content: amounts, phone numbers, order IDs and English words must keep left-to-right order inside the right-to-left text. Type and save an address mixing Urdu and English to confirm it is stored and shown as typed.
37 cases · 10 need a real phone
38 cases · 16 need a real phone
40 cases · 12 need a real phone
40 cases · 13 need a real phone
39 cases · 12 need a real phone
36 cases · 11 need a real phone
99tests runs your cases, AI-generated ones included, on the phones, laptops and browsers your users own. Every finding is verified, serious bugs come with a screen recording, and each case comes back pass, fail, blocked or not run.