Comprehensive Product Testing Improved The Reliability Of A SaaS-Based Payment Services Provider

We were the obvious choice for the client as we have deep expertise and vast experience in testing mobile apps - front-end and backend. During the course of this engagement, we relied on our testers, who knew mobile testing inside out. The first step was to analyze project requirements so that we were ready to create an end-to-end test strategy.

After evaluating project requirements, we formulated the most comprehensive test strategy that perfectly reflected the client's goals. Our test strategy comprised system testing, integration testing, usability testing, regression testing, and unit testing. After we built a robust test strategy, we clarified the responsibilities and roles of every team member. Our team was made of dedicated testers, project coordinators, and a test leader.

After we defined the responsibilities and roles of our testing squad, we checked the environmental setup and its key requirements. As a software testing company with years of experience, we understand the importance of running a complete environment check. The outcomes of a well-monitored environment check help testers zero in on the operating system that can be used to test all the elements present in a mobile app.

After evaluating project requirements, we created a test strategy that mixed manual testing with automated testing. Besides manual testing, we were big on the idea of using automated testing for testing the mobile because of many reasons. First of all, a mobile application has several elements needed to be test-certified on multiple device models and operating systems -Android and iOS. Moreover, an automated QA process works well for mobile apps as they need to be tested more often because of consistent OS upgrades, new device launches, etc.

Our test strategy relied on multiple tools. As a case in point, we went ahead with Postman - which is a platform that we used for testing different APIs that we part of this digital wallet mobile app. Since the e-wallet app had many artifacts, we wanted to build a centralized repository of all their source codes. We used Microsoft Team Foundation Server to build that repository. This tool is now known as Azure DevOps Server.

Since testing any asset involves multiple risks, we documented different risk factors. With all the probable risk factors well-documented, we could predict whenever they were likely to happen. Moreover, we built a comprehensive list of test schedules that gave a clear view of different testing phases. These test schedules even gave the client the visibility of which test case would be executed at what point in time and by which tester.

In addition, regression testing has been an integral part of our mobile app testing strategy. That way, we are empowered to make sure the app is delivering peak performance even after every minute change. Being a trusted mobile app testing company means we understand the value of test groups. That is why we defined different test groups for the project. And these test groups were created only after factoring in different elements: test records maintenance, test reporting, test priorities, status collection, and traceability matrix requirements.

As part of usability testing, we tested the multiple app features - sending and receiving money, making contactless payments, splitting bills, paying for transits, etc. This testing helped us ensure that the end-user can send and receive money from the digital wallet or the linked bank account securely and smoothly. We even tested the payment gateway integration with the app. This particular test ensured that the app showed errors whenever the user keyed in a faulty CVV number. Besides, this test helped us ensure that a user's registered mobile number was getting the OTP generated from the payment gateway.

Moreover, we performed multiple testing on the app's built-in digital wallet. This form of testing helped us ensure that the users could add money to the wallet from their linked bank accounts. Likewise, we tested whether the user could send money from the e-wallet to the linked account seamlessly. These tests on the digital wallet have helped us ensure that the e-wallet reflected the correct amount whenever the funds were debited from it or credited to it.

Our Testing Process

For executing every testing task perfectly, we have a software testing life cycle in place. When we use this testing cycle, we have clear visibility of multiple test schedules that we need to execute to get the job done. Our testing process has helped us debug different components of the mobile app and carry out high-level testing schedules at speed and scale. Here are some of the key steps of the testing process we followed throughout this engagement.

• Gathered and evaluated different project requirements
• Built a comprehensive strategy that included different testing phases
• Developed different test-case designs
• Checked the test environment from end to end
• Executed multiple test cases
• Followed a test cycle closure with well-defined exit criteria