Functional Testing of Buy Now, Pay Later Software to Prevent CX Issues and Speed Up Releases
About Our Customer
The Client is a Gulf-based startup specializing in fintech solutions for customers in the MENA region.
Insufficient Testing of a Buy Now, Pay Later App
The Customer was evolving a Buy Now, Pay Later (BNPL) web application. Since the software was already available to end users, the Customer needed additional manual testing resources to ensure maximum test coverage when releasing new features. Also, the Customer was considering introducing test automation to the ongoing project.
Team Augmentation with an Experienced Test Engineer
The Customer had already cooperated with ScienceSoft on back-end and front-end software development. Satisfied with our team’s professionalism, the Customer turned to ScienceSoft again to augment its team with a qualified test engineer.
ScienceSoft’s test engineer established smooth communication with the Customer’s project manager and the testing team and swiftly dived into the product specifics.
Initially, the Customer was interested in test automation, but after a feasibility study, it was decided to postpone test automation due to the complexity of the software payment functionality. At that stage of the app’s evolution, the Customer decided to invest more in developing and manually testing new functionality.
Throughout three major releases, ScienceSoft’s test engineer worked together with the Customer’s team to perform manual functional testing (including regression testing) of the app on different platforms (macOS, iOS, Android) and in different browsers (Safari, Chrome). Functional testing was performed using the TestRail tool that allowed test engineers to track testing activities and submit testing results. Postman was used to test the software APIs. ScienceSoft’s test engineer was responsible for creating the test suites, while the test lead on the Customer’s side established the test environment and prepared test data.
Apart from the testing activities, ScienceSoft’s test engineer contributed a lot to improving the existing user stories. Many of them were incomplete, poorly written, or overlapping. Our test engineer improved the existing backlog of user stories and set a standard for writing new ones.
Results
ScienceSoft’s tester worked with the Customer’s internal team for eight months. During this time, he helped eliminate a considerable number of functional and UI defects and speed up the releases of the new software modules.
Technologies and Tools
Atlassian Jira, TestRail, Postman
