The software solution involves a multi-carrier shipping software that assists e-commerce projects with computing and displaying the right shipping methods and rates at the checkout. It makes shipping more cost-effective and sales-accelerating. Seamlessly integrative with Magento.

Testing type:
Functional, UX/UI, API
110 hours
2 manual QA engineers
Platforms and tools
Jira, Confluence, Googe sheets, Postman, Swagger, Browserstack


Our team was requested to analyze (make system audit) and perform functional and UI testing the shipping storefront solution (integration) for e-commerce store customers. We were granted with the accesses to the Magento staging environment, shipping integration dashboard, bug-tracking system, confluence sheets with the requirements descriptions, and communication channel for receiving clarifications on demand.


The first step was the analyze of integration’s functionality and decomposition into several smaller basic flows such as: synchronization with Magento, flat and custom shipping rates management, carriers management (international carriers involvement, e.g. Fedex, UPS, etc.) which in total form the entire shipping solution.

Based on these flows we designed the detailed checklist for covering all the aspects of the integration and aligned it with the development team. After getting approval, 2 QA engineers were engaged in simultaneous testing of the whole system. The detected issues have been immediately marked in the checklist and moved to the Jira bug-tracking system after the dev team review.

After completing the first round of functional and UI service evaluation, the QA team also performed grey-box testing (using Swagger and also Postman for API testing) for verification the latest database changes and implementing new operators and parameters and made quick regression testing with the purpose to check if new issues had not been appeared after these changes.


The designed detailed checklist reflected the dynamic and allowed the development team to track current testing progress and results in real time, which eventually allowed to deploy hot-fixes that blocked testing on some steps. In total, 67 functional and UI issues were found with different levels of severity – minor ones to blockers. Our engineers also generated UX improvement suggestions which were also accepted by the dev team. What’s more a couple of requirements gaps were found and conveyed to the dev team as well for finalization. The QA process helped the development team to improve the quality of their service in terms of functionality and user experience. The initially detailed checklist became a good base for further testing rounds.regression testing rounds.