2016 IEEE International Conference on Software Testing, Verification and Validation (ICST) (2016)
Chicago, IL, USA
April 11, 2016 to April 15, 2016
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/ICST.2016.44
Different techniques to automatically generate unit tests for object oriented classes have been proposed, but how to integrate these tools into the daily activities of software development is a little investigated question. In this paper, we report on our experience in supporting industrial partners in introducing the EvoSuite automated JUnit test generation tool in their software development processes. The first step consisted of providing a plugin to the Apache Maven build infrastructure. The move from a research-oriented point-and-click tool to an automated step of the build process has implications on how developers interact with the tool and generated tests, and therefore, we produced a plugin for the popular IntelliJ Integrated Development Environment (IDE). As build automation is a core component of Continuous Integration (CI), we provide a further plugin to the Jenkins CI system, which allows developers to monitor the results of EvoSuite and integrate generated tests in their source tree. In this paper, we discuss the resulting architecture of the plugins, and the challenges arising when building such plugins. Although the plugins described are targeted for the EvoSuite tool, they can be adapted and their architecture can be reused for other test generation tools as well.
Software, Java, Instruments, Manuals, Runtime, Libraries, Servers,
Andrea Arcuri, Jose Campos, Gordon Fraser, "Unit Test Generation During Software Development: EvoSuite Plugins for Maven, IntelliJ and Jenkins", 2016 IEEE International Conference on Software Testing, Verification and Validation (ICST), vol. 00, no. , pp. 401-408, 2016, doi:10.1109/ICST.2016.44