Abstract | ||
---|---|---|
ABSTRACTExtract Method is probably the most commonly used refactoring. Although it may seem quite simple at a first glance, there are many cases that it can become fairly complex. Local variables and parameters can make this refactoring difficult to implement. The whole procedure can also become quite error-prone. The only way to be sure that we performed the refactoring without introducing bugs is by means of testing. Testing, however, seems to many application developers a very bothersome procedure. To facilitate their work we discuss patterns that customize existing testing techniques to the specificities of the Extract Method refactoring. |
Year | DOI | Venue |
---|---|---|
2020 | 10.1145/3424771.3424793 | PLOP |
DocType | Citations | PageRank |
Conference | 0 | 0.34 |
References | Authors | |
0 | 3 |
Name | Order | Citations | PageRank |
---|---|---|---|
Ioannis Megas | 1 | 0 | 0.34 |
Apostolos Zarras | 2 | 293 | 30.20 |
Chris Karelis | 3 | 0 | 0.34 |