Continuous Refactoring in CI: A Preliminary Study on the Perceived Advantages and Barriers
Continuous Refactoring in CI: A Preliminary Study on the Perceived Advantages and Barriers
复制标题
CI 中的持续重构：感知优势和障碍的初步研究
DOI：
--
复制
发表时间：
2018
期刊：
影响因子：
--
通讯作者：
H. Gall
中科院分区：
文献类型：
--
作者：
Carmine Vassallo;Fabio Palomba;H. Gall
根据定义，持续集成（CI）的实践促进了持续的软件质量改进。在采用这种实践的系统中，质量保证通常通过使用静态和动态分析工具（例如，SonarQube）计算总体指标，如可维护性或可靠性测量。此外，开发人员通常定义质量门，即，在每次新提交的更改之后，软件产品必须达到的源代码质量阈值。如果某些质量门失败（例如，可维护性度量低于设定的阈值），开发人员应该重构代码，可能解决一些建议的警告。虽然以前的研究结果表明，重构往往不是在实践中完成，它仍然不清楚是否以及如何采用CI哲学已经改变了开发人员的方式感知和采用重构。在本文中，我们初步研究运行的调查研究，涉及31开发人员如何执行重构CI，他们需要和他们面临的障碍，同时不断重构源代码。
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.
DOI：
10.1109/icsme.2014.75
发表时间：
2014
期刊：
--
影响因子：
--
作者：
Hall M
通讯作者：
Hall M