Reference : An industrial study on the differences between pre-release and post-release bugs |
Scientific congresses, symposiums and conference proceedings : Paper published in a book | |||
Engineering, computing & technology : Computer science | |||
Security, Reliability and Trust | |||
http://hdl.handle.net/10993/41416 | |||
An industrial study on the differences between pre-release and post-release bugs | |
English | |
Rwemalika, Renaud ![]() | |
Kintis, Marinos ![]() | |
Papadakis, Mike ![]() | |
Le Traon, Yves ![]() | |
Lorrach, Pierre ![]() | |
30-Sep-2019 | |
Proceedings of 35th IEEE International Conference on Software Maintenance and Evolution | |
IEEE | |
11 | |
Yes | |
No | |
International | |
35th IEEE International Conference on Software Maintenance and Evolution | |
from 30-09-2019 to 04-10-2019 | |
Cleveland, OH | |
USA | |
[en] industrial study ; pre-release bug fixes ; post-release bug fixes ; revision histories ; quality assurance | |
[en] Software bugs constitute a frequent and common issue of software development. To deal with this problem, modern software development methodologies introduce dedicated quality assurance procedures. At the same time researchers aim at developing techniques capable of supporting the early discovery and fix of bugs. One important factor that guides such research attempts is the characteristics of software bugs and bug fixes.
In this paper, we present an industrial study on the characteristics and differences between pre-release bugs, i.e. bugs detected during software development, and post-release bugs, i.e. bugs that escaped to production. Understanding such differences is of paramount importance as it will improve our understanding on the testing and debugging support that practitioners require from the research community, on the validity of the assumptions of several research techniques, and, most importantly, on the reasons why bugs escape to production. To this end, we analyze 37 industrial projects from our industrial partner and document the differences between pre-release bugs and post-release bugs. Our findings suggest that post-release bugs are more complex to fix, requiring developers to modify several source code files, written in different programming languages, and configuration files, as well. We also find that approximately 82% of the post-release bugs involve code additions and can be characterized as "omission" bugs. Finally, we conclude the paper with a discussion on the implications of our study and provide guidance to future research directions. | |
Interdisciplinary Centre for Security, Reliability and Trust (SnT) > Security Design and Validation Research Group (SerVal) | |
Fonds National de la Recherche - FnR ; BGL BNP Paribas | |
CODEMATES | |
Researchers ; Professionals | |
http://hdl.handle.net/10993/41416 | |
FnR ; FNR11686509 > Michail Papadakis > CODEMATES > COntinuous DEvelopment with Mutation Analysis and TESting > 01/09/2018 > 31/08/2021 > 2017 |
File(s) associated to this reference | ||||||||||||||
Fulltext file(s):
| ||||||||||||||
All documents in ORBilu are protected by a user license.