首页> 外文会议>IEEE/ACM International Conference on Mining Software Repositories >Predicting Co-Changes between Functionality Specifications and Source Code in Behavior Driven Development
【24h】

Predicting Co-Changes between Functionality Specifications and Source Code in Behavior Driven Development

机译:预测行为驱动开发中功能规范和源代码之间的协同变化

获取原文

摘要

Behavior Driven Development (BDD) is an agile approach that uses. feature files to describe the functionalities of a software system using natural language constructs (English-like phrases). Because of the English-like structure of. feature files, BDD specifications become an evolving documentation that helps all (even non-technical) stakeholders to understand and contribute to a software project. After specifying a. feature files, developers can use a BDD tool (e.g., Cucumber) to automatically generate test cases and implement the code of the specified functionality. However, maintaining traceability between. feature files and source code requires human efforts. Therefore,. feature files can be out-of-date, reducing the advantages of using BDD. Furthermore, existing research do not attempt to improve the traceability between. feature files and source code files. In this paper, we study the co-changes between. feature files and source code files to improve the traceability between. feature files and source code files. Due to the English-like syntax of. feature files, we use natural language processing to identify co-changes, with an accuracy of 79%. We study the characteristics of BDD co-changes and build random forest models to predict when a. feature files should be modified before committing a code change. The random forest model obtains an AUC of 0.77. The model can assist developers in identifying when a. feature files should be modified in code commits. Once the traceability is up-to-date, BDD developers can write test code more efficiently and keep the software documentation up-to-date.
机译:行为驱动开发(BDD)是一种使用的敏捷方法。使用自然语言构造描述软件系统的功能文件(类似英文短语)。因为类似的英语结构。功能文件,BDD规范成为一种不断发展的文档,可以帮助所有(偶数非技术)利益相关者了解和贡献软件项目。指定a后。功能文件,开发人员可以使用BDD工具(例如,黄瓜)自动生成测试用例并实现指定功能的代码。但是,维持之间的可追溯性。功能文件和源代码需要人力努力。所以,。功能文件可能已过时,从而减少使用BDD的优势。此外,现有的研究不会试图改善之间的可追溯性。功能文件和源代码文件。在本文中,我们研究了相同的变化。要素文件和源代码文件以提高介于之间的可追溯性。功能文件和源代码文件。由于英语类似的语法。功能文件,我们使用自然语言处理来识别相同的变化,精度为79%。我们研究了BDD共同变化的特点,并建立了随机林模型来预测A.在进行代码更改之前,应修改功能文件。随机森林模型获得0.77的AUC。该模型可以帮助开发人员识别a。应在代码中修改功能文件。一旦可追溯性是最新的,BDD开发人员就可以更有效地编写测试代码并保持软件文档最新。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号