Our core responsibility is supporting individual suppliers and companies that use the client’s P2P solution.
1) Testing for the new product under development The work started with standard manual testing: functional testing covering the verification of new features and regression testing. At first, the documentation was absent. The QA engineers only had a checklist to run during each regression session. The checklist was updated with new items after each release.
2) Enabling platform customization After the company signed one big client, the need to assign a dedicated QA specialist to work with it arose. The P2P platform was built on standard Magento CMS. However, Magento’s functionality was modified and extended with each release. Eventually, it was customized to the extent that the backend started to resemble Magento 2, though the platform didn’t migrate to the newer version.
Around 10% of the functionality remained from its original platform. The rest was developed from scratch upon it. Our QA team was at the platform’s origin, testing each feature a development team created.
3) Scaling the product and the QA team accordingly The number of QA specialists working with the product grew, along with the workload that triggered the need for new roles. Currently, ten experts from QA Madness work with the client full-time and are involved in different teams: quality assurance, support, automation, implementation, and product teams.
Each team has a separate board in Jira. The pool of tasks the QA Madness specialists cover includes:
- Functional and regression testing.
- Verification of tasks after fixes.
- Work with clients’ tickets.
- Verification of client requests, assigning tasks, and setting priorities.
- Support tasks (checking issues reported by clients).
- Test automation and test suite maintenance.
- Test case writing and work with documentation.