Before implementing the new test strategy, we conducted an initial feasibility analysis to verify whether the application build was helpful for further testing activities. This testing was pivotal in identifying stability issues that might disrupt the app’s quality and purpose. This helped the dev team to control the number of dot releases/hotfixes.

We made the QA process more manageable and transparent by implementing agile testing practices in DevOps. We ensured that all our testing processes were light and nimble to help the dev team get help from QA as and when needed. We ensured appropriate QA strategies were implemented to curb defects even in the initial stage.

We performed different types of testing, such as migration and API testing, to mimic the real production environment in different market regions using backend tools such as DOC tool and TOCO dashboard. We changed the reporting module per the dev teams’ current communication practice over slack channels to merge our QA processes with existing driver teams, such as marketing and product teams.

We collected reviews from app stores such as Apple Appstore and Google Playstore and third-party review portals like Reddit and Sitejabber to bring out test scenarios experienced by real-time users. We also implemented a testing activity of collecting end-user feedback to make the dev team aware of the enhancements needed to excel in this heavily competitive driver app market. Our team also ensured legal compliance by testing related requirements and continued providing QA support and management for the app’s QA processes.