On rapid releases and software testing: a case study and a semi-systematic literature review

@article{Mntyl2014OnRR,
  title={On rapid releases and software testing: a case study and a semi-systematic literature review},
  author={Mika M{\"a}ntyl{\"a} and Bram Adams and Foutse Khomh and Emelie Engstr{\"o}m and Kai Petersen},
  journal={Empirical Software Engineering},
  year={2014},
  volume={20},
  pages={1384-1425}
}
Large open and closed source organizations like Google, Facebook and Mozilla are migrating their products towards rapid releases. [...] Key Result However, empirical studies proving evidence of the claimed advantages and disadvantages of rapid releases are scarce.Expand
The impact of rapid release cycles on the integration delay of fixed issues
TLDR
The results suggest that rapid release cycles may not be a silver bullet for the rapid delivery of new content to users and that the benefits of rapid releases are increased software stability and user feedback. Expand
Releasing fast and slow: an exploratory case study at ING
TLDR
An exploratory case study of rapid releases at ING, a large banking company that develops software solutions in-house, to characterize rapid releases is presented. Expand
Releasing Fast and Slow: An Exploratory Case Study at ING
The appeal of delivering new features faster has led many software projects to adopt rapid releases. However, it is not well understood what the effects of this practice are. This paper presents anExpand
The Impact of Switching to a Rapid Release Cycle on the Integration Delay of Addressed Issues - An Empirical Study of the Mozilla Firefox Project
TLDR
It is observed that addressed issues take a median of 50 days longer to be integrated in rapid Firefox releases than the traditional ones, suggesting that rapid release cycles may not be a silver bullet for the rapid delivery of addressed issues to users. Expand
Releasing Fast and Slow : An Exploratory
The appeal of delivering new features faster has led many software projects to adopt rapid releases. However, it is not well understood what the effects of this practice are. This paper presents anExpand
Releasing Fast and Slow An Exploratory
The appeal of delivering new features faster has led many software projects to adopt rapid releases. However, it is not well understood what the effects of this practice are. This paper presents anExpand
On the impact of release policies on bug handling activity: A case study of Eclipse
TLDR
Eclipse’s bug handling process is becoming more stable over time, with a decreasing number of reported bugs before releases, an increasing bug fixing rate and an increasingly balanced bug handling workload before and after releases. Expand
Prioritizing manual test cases in rapid release environments
TLDR
The conclusion of the paper is that test cases in rapid release environments can be very effectively prioritized for execution, based on their historical failure knowledge, rather than other changes in the process. Expand
Characterizing Rapid Releases in a Large Banking Company: A Case Study
TLDR
A case study of rapid releases at ING, a large Netherlands-based internationally operating bank that develops software solutions in-house, is presented, which resulted in a mixed environment of rapid and traditional teams. Expand
Frequent Releases in Open Source Software: A Systematic Review
TLDR
This study provides an up-to-date and structured understanding of the software release approaches in the context of OSS projects based on findings systematically collected from a list of relevant references in the last decade. Expand
...
1
2
3
4
5
...

References

SHOWING 1-10 OF 108 REFERENCES
On Rapid Releases and Software Testing
TLDR
This paper investigates the changes in software testing effort after moving to rapid releases, and analyzes 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. Expand
Do faster releases improve software quality? An empirical case study of Mozilla Firefox
TLDR
It is found that with shorter release cycles, users do not experience significantly more post-release bugs and bugs are fixed faster, yet users experience these bugs earlier during software execution (the program crashes earlier). Expand
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
Getting software released to users is often a painful, risky, and time-consuming process. This groundbreaking new book sets out the principles and technical practices that enable rapid, incrementalExpand
The Secret Life of Patches: A Firefox Case Study
TLDR
A quantitative comparison showed that while the patch lifecycle remains mostly unchanged after switching to rapid release, the patches submitted by casual contributors are disproportionately more likely to be abandoned compared to core contributors, suggesting that patches from casual developers should receive extra care to both ensure quality and encourage future community contributions. Expand
Benefits and limitations of automated software testing: Systematic literature review and practitioner survey
TLDR
The survey showed that benefits of test automation were related to test reusability, repeatability, test coverage and effort saved in test executions, and 80% of the practitioners disagreed with the vision that automated testing would fully replace manual testing. Expand
Looking for bugs in all the right places
TLDR
Three versions of the negative binomial regression model are explored, as well as a simple lines-of-code based model, to make predictions for this system and the differences observed from the earlier studies are discussed. Expand
How much really changes? A case study of firefox version evolution using a clone detector
  • T. Lavoie, E. Merlo
  • Computer Science
  • 2013 7th International Workshop on Software Clones (IWSC)
  • 2013
TLDR
A case study of Firefox for which the development release cycle changed from a slow release cycle to a fast release cycle two years ago, the results indicate a significant decrease in the overall difference between many versions in thefast release cycle. Expand
Applied Quality Assurance Methods under the Open Source Development Model
TLDR
The aim of this research is to improve the understanding of QA practices under the OSSD model and provide evidence for Raymondpsilas lifecycle and show that OSS projects leverage their communities effectively. Expand
Achieving scalable model-based testing through test case diversity
TLDR
A family of similarity-based test case selection techniques for test suites generated from state machines is introduced and a method to identify optimal tradeoffs between the number of test cases to run and fault detection is proposed. Expand
Agile, open source, distributed, and on-time: inside the eclipse development process
TLDR
This talk sheds light on the key practices of the Eclipse development process - from the development mantras "Always Beta", "Milestones First", "API First", and "Performance First" to practices such as ensuring quality through multiple feedback loops. Expand
...
1
2
3
4
5
...