Emails
Emails Not Sent
Emails the platform should have sent were never triggered, so users would not have received messages they were waiting for.
Founder Project · Logistics
React Native Localization Testing in 10 Languages, Plus Web and API Automation
Cypress on the web, Appium on React Native apps in 10 languages, plus Playwright, Postman and JMeter on a certificate system, led by our founder.
A founder project: work our founder, Muhammad Usman, led before he started SprintSynergy in 2021. The client is not named.
founder-project / logisticsCompleted
- Client
- Global logistics company, unnamed
- Platforms
- Member benefits platform (web frontend, admin panel, React Native apps for Android and iOS); digital certificate system (web and APIs)
- Role
- Our founder led QA on both
- Web Stack
- Cypress, Cucumber Studio, MailSlurp, Microsoft Azure pipelines, Jira
- Mobile Stack
- Java, Appium, Selenium, TestNG, Maven, BrowserStack, Jenkins, Allure
- Devices
- 15+ device and OS combinations on BrowserStack
- Certificates
- Playwright, Postman, JMeter
500+Automated Web Tests
400+Automated Mobile Tests
80%of Web Manual Test Cases Automated
90%of Mobile Manual Test Cases Automated
10Languages Checked in Mobile Automation
The Result
What Was in Place by the End
- 80% of the web and 90% of the mobile manual test cases automated, in Cypress and Appium.
- One app checked in 10 languages on 15+ device and OS combinations through BrowserStack.
- Eleven bugs found across web, mobile and APIs, from emails that were never sent to certificate APIs that stopped responding under load.
Overview
Two Platforms, Web and Mobile
Our founder led QA on two platforms for a global logistics company. The first is a member benefits platform, where members get benefits from partners, organized by hubs in several countries. It runs on the web and in React Native apps for Android and iOS. The second is a digital certificate system that creates certificates and verifies them. On the benefits platform, the work covered a test plan, 600+ manual test cases and a Cypress framework with 500+ automated tests. A Java and Appium framework added 400+ automated mobile tests, including translation checks in 10 languages. On the certificate system, it covered Playwright automation, API tests in Postman and backend performance tests in JMeter.
Platform 1
Member Benefits Platform
Member frontend, admin panel, emails and exports, plus React Native apps for Android and iOS in 10 languages.
CypressCucumber StudioMailSlurpAzure PipelinesAppiumJavaTestNGBrowserStackJenkinsAllure
Platform 2
Digital Certificate System
Creating and verifying certificates, the APIs behind them and backend performance under load.
PlaywrightPostmanJMeter
The Problem
One Change, Many Places
The benefits platform connects three groups: members, partners who offer benefits and the admin team that manages both. Each hub, in each country, has its own partners and benefits. A change in one place can break what members see somewhere else.
The same journeys also run in apps on Android and iOS, in 10 languages. A screen that works in English on one phone can break in Arabic on another, or show text that was never translated.
The certificate system carries a different risk. A certificate that is created wrongly, or that fails verification, defeats the purpose of the system. Its APIs also have to keep responding when many requests arrive at once.
What Was Tested
Web, Mobile and APIs
- Member Benefits Platform, Web: the member frontend and the admin panel, where partners and benefits are added and managed; the emails the platform sends; data exports from the admin panel.
- Member Benefits Platform, Mobile: the React Native apps for Android and iOS, on 15+ device and OS combinations, with the app's text checked in 10 languages: English, Arabic, French, Indonesian, Korean, Portuguese, Russian, Spanish, Thai and Vietnamese.
- Certificate System: creating and verifying certificates, automated in Playwright; the APIs, with Postman test cases for responses, status codes and messages; backend performance under load, in JMeter.
How It Was Built
Cypress, Appium and BrowserStack
- An automation architecture document and a test plan.
- 600+ manual test cases for the frontend and the admin panel, written and kept in Cucumber Studio.
- A Cypress framework with 500+ automated tests, built data-driven. Test data is kept apart from the test code, so one test runs once for each data set.
- CI/CD pipelines in Microsoft Azure that run the Cypress suite.
- MailSlurp test inboxes that check the platform's emails are sent and arrive.
- A mobile automation framework built from scratch in Java with Appium, Selenium, TestNG and Maven, for the React Native apps on Android and iOS: 400+ automated tests.
- BrowserStack to run the mobile tests on 15+ device and OS combinations.
- Jenkins and Allure reporting for the mobile test runs.
- Translation checks in the mobile automation, confirming the app's text is properly translated in each of 10 languages.
- Jira for tracking the work and the bugs.
- For the certificate system: a Playwright framework, Postman API test cases and JMeter performance tests.
What Testing Found
Eleven Bugs on Three Fronts
Member Benefits Platform
Admin Panel
Partners and Benefits Could Not Be Added
The admin panel failed to add them, which blocked the team from adding new offers for members.
Member Frontend
Partner Logos Missing
Logos did not show, so members could not recognize the partner behind a benefit.
Admin Panel
Export Not Working
The admin team could not export data.
Member Mobile Apps
Mobile
Data Not Loading Properly
Screens did not load their data correctly, so members saw incomplete information.
Mobile
Swipe Not Working
Swipe gestures failed, so members could not move through content the way the app was designed.
Mobile
Images Not Showing Properly
Images did not display correctly in the apps.
Mobile
Slow Data Loading
Data took too long to load, leaving members waiting on blank or partial screens.
Certificate System
Certificates
Certificates Not Generated Correctly
The core output of the system was wrong.
APIs
Inaccurate API Responses
Status codes and messages did not match what had happened, so a calling system could not tell success from failure.
APIs · JMeter
APIs Failing Under Load
In JMeter tests, the APIs stopped responding when the load went up.
What Was Delivered
Handed Over
- 600+ manual test cases, kept in Cucumber Studio.
- 500+ automated tests in a data-driven Cypress framework, run from pipelines in Microsoft Azure.
- 80% of the web manual test cases automated, across both web platforms.
- 400+ automated mobile tests in a Java and Appium framework, run on BrowserStack with Jenkins and Allure, with translation checks in 10 languages.
- 90% of the mobile manual test cases automated.
- Email checks with MailSlurp test inboxes.
- Playwright automation, Postman API test cases and JMeter performance tests for the certificate system.
Questions
Frequently Asked Questions
Test data is kept apart from the test code, so one test runs once for each data set. The Cypress framework on the benefits platform was built this way.
More Case Studies
All Case StudiesTesting an App That Runs in Many Languages?
Book a free 30-minute QA strategy call. A written QA plan follows within 48 hours.
Book a Free QA Strategy Call