QA Madness provided a dedicated team – the specialists working on a project full-time and as a full-fledged part of the client’s tech team. The team consisted of manual and automation testing experts.
After the onboarding, which took several days, the specialists got fully involved in the working process. All testing tasks were divided between the team, and each QA engineer had a specific area of responsibility, accompanied by:
- communication with developers, analysts, and PM;
- writing of the test case suite and its maintenance;
- presentation of their work in daily meetings;
- setting up a manual testing process, including functional, performance, and UI testing;
- running autotests and preparing the scripts so the client’s team could run and maintain them in the future without our help.
Since the main product’s benefit was using AI technology, assessing not just functional quality issues but also the potential deterioration of the entire system’s behavior was imperative. The responsibility of the AQA engineer involved evaluating the speed and efficacy with which modifications in both AI and non-AI components could be incorporated and ensuring that the consequences of failures could be minimized.