arXivDaily arXiv每日学术速递 周一至周五更新
arXiv 2203.09134cs.SE
收藏

Eclipse Stable内部接口缺陷的实证研究

An Empirical Study of Bugs in Eclipse Stable Internal Interfaces

Simon Kawuma, Evarist Nabaasa

摘要:

Eclipse框架是一个流行且广泛使用的框架,已经发展了十多年。该框架提供稳定接口(API)和不稳定接口(非API)。尽管Eclipse不鼓励应用程序开发人员使用非API,但这会导致他们的系统在移植到新的框架版本时失败。以前的研究表明,与使用新引入的非API的应用程序相比,使用相对较旧的非API的应用程序更有可能与新版本兼容。此外,从我们之前对Eclipse内部接口稳定性的研究中,我们发现随着Eclipse框架的发展,存在327K稳定的非API方法。在同一项研究中,我们建议Eclipse接口提供者可以使用327K稳定的非API方法作为提升到稳定接口的可能候选者。然而,由于非API不受支持并且被认为是不成熟的,即,可能包含错误,为此,需要首先调查稳定的非API的可能错误,然后才能将其提升为API。在这项研究中,我们使用Sonarqube软件质量工具对稳定的非API进行了实证研究,以发现可能的错误。我们发现,超过79.8%的包含旧的稳定非API方法的类没有bug。接口提供商和用户都可以使用这项研究的结果作为起点,以分析哪些接口经过了良好的测试,并估计在为给定的eclipse版本执行bug修复时可能涉及多少工作。

英文摘要:

TThe Eclipse framework is a popular and widely used framework that has been evolving for over a decade. The framework provides both stable interfaces (APIs) and unstable interfaces (non-APIs). Despite being discouraged by Eclipse, application developers often use non-APIs which cause their systems to fail when ported to new framework releases. Previous studies showed that applications using relatively old non-APIs are more likely to be compatible with new releases compared to the ones that used newly introduced non-APIs. Furthermore, from our previous study about the stability of Eclipse internal interfaces, we discovered that there exist 327K stable non-API methods as the Eclipse framework evolves. In the same study, we recommended that 327K stable non-API methods can be used by Eclipse interface providers as possible candidates for promotion to stable interfaces. However, since non-APIs are unsupported and considered to be immature i.e., can contain bugs, to this end there exist a need to first investigate the stable non-APIs for possible bugs before they can be promoted to APIs. In this study, we empirically investigated the stable non-API for possible bugs using Sonarqube software quality tool. We discovered that over 79.8% classes containing old stable non-APIs methods have zero bugs. Results from this study can be used by both interface providers and users as a starting point to analyze which interfaces are well tested and also estimate how much work could be involved when performing bug fixing for a given eclipse release.

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑