Change search
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
On rapid releases and software testing: a case study and a semi-systematic literature review
Show others and affiliations
2015 (English)In: Empirical Software Engineering, ISSN 1382-3256, Vol. 20, no 5, 1384-1425 p.Article in journal (Refereed) Published
Abstract [en]

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 in the context of a case study on Mozilla Firefox, and performs a semi-systematic literature review. The case study analyzes 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 triangulates our findings with a Mozilla QA engineer. We find that rapid releases have a narrower test scope that enables a deeper investigation of the features and regressions with the highest risk. Furthermore, rapid releases make testing more continuous and have proportionally smaller spikes before the main release. However, rapid releases make it more difficult to build a large testing community , and they decrease test suite diversity and make testing more deadline oriented. In addition, our semi-systematic literature review presents the benefits, problems and enablers of rapid releases from 24 papers found using systematic search queries and a similar amount of papers found through other means. The literature review shows that rapid releases are a prevalent industrial practice that are utilized even in some highly critical domains of software engineering, and that rapid releases originated from several software development methodologies such as agile, open source, lean and internet-speed software development. However, empirical studies proving evidence of the claimed advantages and disadvantages of rapid releases are scarce.

Place, publisher, year, edition, pages
Springer Netherlands, 2015. Vol. 20, no 5, 1384-1425 p.
Keyword [en]
Agile releases, Bugs, Builds, Mozilla, Open-source, Release model, Software testing
National Category
Software Engineering
Identifiers
URN: urn:nbn:se:bth-6527DOI: 10.1007/s10664-014-9338-4ISI: 000360671500007Local ID: oai:bth.se:forskinfo3BBC078A48EB6F66C1257D9A00459299OAI: oai:DiVA.org:bth-6527DiVA: diva2:834045
Available from: 2014-11-24 Created: 2014-11-24 Last updated: 2015-10-20Bibliographically approved

Open Access in DiVA

No full text

Other links

Publisher's full text

Search in DiVA

By author/editor
Petersen, Kai
By organisation
School of Computing
Software Engineering

Search outside of DiVA

GoogleGoogle Scholar

Altmetric score

Total: 50 hits
CiteExportLink to record
Permanent link

Direct link
Cite
Citation style
  • apa
  • harvard1
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf