Ongoing QA Support for the Enterprise Procure-to-Pay Software Provider
Challenge
The client operates a B2B procurement and procure-to-pay platform that connects enterprise organizations with suppliers and supports spending management. QA Madness joined the project while the product was still under development, when the client needed to validate its functionality before a broader market release.
A major challenge was the platform’s high degree of customization. Although the front end could look similar for different customers, each implementation could have its own configuration and functionality. These variations continued to grow as new enterprise customers requested individual changes, while the related configurations were not always sufficiently documented.
As the product and customer base expanded, the QA workload increased as well. The client needed to test new functionality, maintain regression coverage, monitor post-release changes, support customer requests, and scale the QA team according to the number and complexity of platform variations.
The client operates a B2B procurement and procure-to-pay platform that connects enterprise organizations with suppliers and supports spending management. QA Madness joined the project while the product was still under development, when the client needed to validate its functionality before a broader market release.
A major challenge was the platform’s high degree of customization. Although the front end could look similar for different customers, each implementation could have its own configuration and functionality. These variations continued to grow as new enterprise customers requested individual changes, while the related configurations were not always sufficiently documented.
As the product and customer base expanded, the QA workload increased as well. The client needed to test new functionality, maintain regression coverage, monitor post-release changes, support customer requests, and scale the QA team according to the number and complexity of platform variations.
Solution
QA Madness started with manual functional and regression testing of the platform under development. At first, there was no formal testing documentation, so QA engineers worked with a regression checklist and continuously updated it with new items after releases. As the platform evolved, the team introduced more comprehensive test cases and documentation to preserve project knowledge and improve testing efficiency.
The platform was based on Magento CMS, but its functionality was extensively modified and extended over time. QA Madness specialists were involved from the early stages of feature development and tested new functionality as it was introduced. When the client acquired a major customer requiring a dedicated configuration, a QA specialist was assigned specifically to that implementation.
As the workload grew, QA Madness scaled the team and introduced different roles covering quality assurance, support, automation, implementation, and product activities. Currently, 10 QA Madness specialists work with the client full-time. Their responsibilities include functional and regression testing, verification after fixes, customer ticket handling, test automation and maintenance, test case writing, documentation, and product analysis. Separate Jira boards are used for the different teams and task areas.
QA Madness started with manual functional and regression testing of the platform under development. At first, there was no formal testing documentation, so QA engineers worked with a regression checklist and continuously updated it with new items after releases. As the platform evolved, the team introduced more comprehensive test cases and documentation to preserve project knowledge and improve testing efficiency.
The platform was based on Magento CMS, but its functionality was extensively modified and extended over time. QA Madness specialists were involved from the early stages of feature development and tested new functionality as it was introduced. When the client acquired a major customer requiring a dedicated configuration, a QA specialist was assigned specifically to that implementation.
As the workload grew, QA Madness scaled the team and introduced different roles covering quality assurance, support, automation, implementation, and product activities. Currently, 10 QA Madness specialists work with the client full-time. Their responsibilities include functional and regression testing, verification after fixes, customer ticket handling, test automation and maintenance, test case writing, documentation, and product analysis. Separate Jira boards are used for the different teams and task areas.
Results
The long-term QA partnership established a structured approach to testing and project knowledge management. Test cases and software requirements were documented and continuously updated, making it easier to maintain product knowledge, communicate across teams, and perform testing across the platform’s evolving configurations.
QA Madness also established a flexible team model that could be adjusted according to current customer and product requirements. New QA specialists were onboarded with product and process knowledge before joining the relevant team, while dedicated support was provided for individual customer configurations.
The engagement currently involves 10 full-time specialists and more than 1,500 hours per month dedicated to manual and automated testing, documentation, product analysis, and customer tickets. The team supports more than 20 custom platform variations, processes approximately 250 tickets per month, and runs around 2,700 automated tests per test run.
The long-term QA partnership established a structured approach to testing and project knowledge management. Test cases and software requirements were documented and continuously updated, making it easier to maintain product knowledge, communicate across teams, and perform testing across the platform’s evolving configurations.
QA Madness also established a flexible team model that could be adjusted according to current customer and product requirements. New QA specialists were onboarded with product and process knowledge before joining the relevant team, while dedicated support was provided for individual customer configurations.
The engagement currently involves 10 full-time specialists and more than 1,500 hours per month dedicated to manual and automated testing, documentation, product analysis, and customer tickets. The team supports more than 20 custom platform variations, processes approximately 250 tickets per month, and runs around 2,700 automated tests per test run.