Abstract
Large open and closed source organizations like Google, Facebook and Mozilla are migrating their products towards rapid releases. While this allows faster time-to-market and user feedback, it also implies less time for testing and bug fixing. Since initial research results indeed show that rapid releases fix proportionally less reported bugs than traditional releases, this paper investigates the changes in software testing effort after moving to rapid releases. We analyze the results of 312,502 execution runs of the 1,547 mostly manual system-level test cases of Mozilla Firefox from 2006 to 2012 (5 major traditional and 9 major rapid releases), and triangulated our findings with a Mozilla QA engineer. In rapid releases, testing has a narrower scope that enables deeper investigation of the features and regressions with the highest risk, while traditional releases run the whole test suite. Furthermore, rapid releases make it more difficult to build a large testing community, forcing Mozilla to increase contractor resources in order to sustain testing for rapid releases.
Ref
Mäntylä M. V., Khomh F.,Adams B, Engström, E. and Petersen K., On Rapid Releases and Software Testing, in Proceedings of the 29th IEEE International Conference on Software Maintenance (ICSM), 22 - 28 September 2013 - Eindhoven, The Netherlands.
Attachments:
Rapid_Releases_and_Software_Testing.png (image/png)
Rapid_Releases_and_Software_Testing.png (image/png)
