On Rapid Releases and Software Testing

Mika Mäntylä, Foutse Khomh, Bram Adams, Emelie Engström, Petersen Kai

Forskningsoutput: Kapitel i bok/rapport/Conference proceedingKonferenspaper i proceedingPeer review


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 Fire fox 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.
Titel på värdpublikation[Host publication title missing]
RedaktörerO'Conner Lisa
FörlagIEEE - Institute of Electrical and Electronics Engineers Inc.
StatusPublished - 2013
Evenemang29th IEEE International Conference on Maintenance (ICSM), 2013 - Eindhoven, Nederländerna
Varaktighet: 2013 sep. 222013 sep. 28


ISSN (tryckt)1063-6773


Konferens29th IEEE International Conference on Maintenance (ICSM), 2013

Ämnesklassifikation (UKÄ)

  • Datavetenskap (datalogi)


Utforska forskningsämnen för ”On Rapid Releases and Software Testing”. Tillsammans bildar de ett unikt fingeravtryck.

Citera det här