Header

UZH-Logo

Maintenance Infos

Continuous Refactoring in CI: A Preliminary Study on the Perceived Advantages and Barriers


Vassallo, Carmine; Palomba, Fabio; Gall, Harald (2018). Continuous Refactoring in CI: A Preliminary Study on the Perceived Advantages and Barriers. In: 2018 IEEE International Conference on Software Maintenance and Evolution, ICSME 2018, Madrid, 23 September 2018 - 29 September 2018, 564-568.

Abstract

By definition, the practice of Continuous Integration (CI) promotes continuous software quality improvement. In systems adopting such a practice, quality assurance is usually performed by using static and dynamic analysis tools (e.g., SonarQube) that compute overall metrics such as maintainability or reliability measures. Furthermore, developers usually define quality gates, i.e., source code quality thresholds that must be reached by the software product after every newly committed change. If certain quality gates fail (e.g., a maintainability metric is below a settled threshold), developers should refactor the code possibly addressing some of the proposed warnings. While previous research findings showed that refactoring is often not done in practice, it is still unclear whether and how the adoption of a CI philosophy has changed the way developers perceive and adopt refactoring. In this paper, we preliminarily study—running a survey study that involves 31 developers—how developers perform refactoring in CI, which needs they have and the barriers they face while continuously refactor source code.

Abstract

By definition, the practice of Continuous Integration (CI) promotes continuous software quality improvement. In systems adopting such a practice, quality assurance is usually performed by using static and dynamic analysis tools (e.g., SonarQube) that compute overall metrics such as maintainability or reliability measures. Furthermore, developers usually define quality gates, i.e., source code quality thresholds that must be reached by the software product after every newly committed change. If certain quality gates fail (e.g., a maintainability metric is below a settled threshold), developers should refactor the code possibly addressing some of the proposed warnings. While previous research findings showed that refactoring is often not done in practice, it is still unclear whether and how the adoption of a CI philosophy has changed the way developers perceive and adopt refactoring. In this paper, we preliminarily study—running a survey study that involves 31 developers—how developers perform refactoring in CI, which needs they have and the barriers they face while continuously refactor source code.

Statistics

Citations

Dimensions.ai Metrics
4 citations in Web of Science®
7 citations in Scopus®
Google Scholar™

Altmetrics

Downloads

2 downloads since deposited on 29 Jan 2021
2 downloads since 12 months
Detailed statistics

Additional indexing

Item Type:Conference or Workshop Item (Paper), refereed, original work
Communities & Collections:03 Faculty of Economics > Department of Informatics
Dewey Decimal Classification:000 Computer science, knowledge & systems
Scopus Subject Areas:Physical Sciences > Safety, Risk, Reliability and Quality
Physical Sciences > Software
Language:English
Event End Date:29 September 2018
Deposited On:29 Jan 2021 05:50
Last Modified:30 Jan 2021 21:01
Publisher:IEEE
OA Status:Green
Publisher DOI:https://doi.org/10.1109/ICSME.2018.00068
Related URLs:https://ieeexplore.ieee.org/document/8530066
Other Identification Number:merlin-id:20336

Download

Green Open Access

Download PDF  'Continuous Refactoring in CI: A Preliminary Study on the Perceived Advantages and Barriers'.
Preview
Content: Accepted Version
Filetype: PDF
Size: 108kB
View at publisher