Table 1 Classification according to the reasons for defect (the reasons are defined by 9 in paper An Empirical Study of Refactoring Engine Bugs)
All bugs identified in the case study are explained in detail so that they could be validated by other researchers. The bug list is publicly available here.
For each bug, we present the code before and after refactoring, the expected results, explanations, and error messages generated by compilers(if there is any)
Feature Library: Features derived from the collected bug reports and test cases.
Analyzed Test Cases: Test cases collected and analyzed in the case study.
Analyzed Bug Reports: Public bug reported collected and analyzed the case study.
1.Requirements
. JDK == 17
• Eclipse, version 2024.3
• NetBeans, version 21
• VScode-java, version 1.22.0
• IntelliJ IDEA, version 2024.1
2.Step-by-step tutorial
Download the implementation at: git clone [email protected]:assdfsdafasfa/OpenPaper.git
- A tool that performs automated execution of refactoring by calling refactoring engines(Auto-RefactoringbyEclipse and Auto-RefactoringbyIDEA) API.
(1) Import Project
import->Existing Projects into Workspace->Auto-RefactoringbyEclipse->plugin.xml->Launch an Eclipse application
open-> Auto-RefactoringbyIDEA->EveryRefactoring
(2) Sequential run refactoring in Eclipse and IntelliJ IDEA, and Save code after refactoring.
(3) Compare Refactoring Codes.
-
We provide prompts designed for 7 types of refactoring.
Paper: Systematic Testing of Refactoring Engines on Real Software Projects BaeLine URL