Frequent regression testing was mandatory every week due to frequent UI changes and other minor adjustments made in the App. Additionally, one major release was scheduled weekly to introduce added functionalities or new features.
Extreme time consumption during manual testing
Manual testers from the client side did not have enough time to test all the workflows before each release due to the frequent release schedule.As a result, both the QA cycle and the release cycle experienced delays due to manually handled regression tests, as bugs identified during manual regression testing had to be rectified by software developers and then retested manually.
Delayed release cycles and associated costs
The frequent releases addressing minor issues fully occupied the manual testers with regression testing, thereby causing delays in releasing new features or updates to existing features/functionality. They needed to be allocated time to thoroughly test major releases containing new features or added functionalities. Additionally, the repeated manual testing of common modules for each regression following minor issues increased the testing costs. Consequently, they sought a solution to accelerate the entire release cycle, in addition to addressing the need for expediting the QA cycle.
