Automatic Refactoring Method to Remove Eager Test Smell

• Adriano Pizzini Pontifícia Universidade Católica do Paraná https://orcid.org/0000-0001-5606-9136
• Sheila Reinehr Pontifícia Universidade Católica do Paraná https://orcid.org/0000-0001-9430-7713
• Andreia Malucelli Pontifícia Universidade Católica do Paraná https://orcid.org/0000-0002-0929-1874

Resumo

Unit tests are artifacts generated during the development process to identify software errors early. Unit tests can be affected by Test Smells (TS), which are defined as poorly designed tests due to bad programming practices implemented in unit test code. Problems caused by TS negatively impact the efficiency of developers and the understanding and maintenance of unit tests. Reducing the problems caused by TS can occur through refactoring activities. Despite the existence of studies that seek to identify the occurrence of TS in unit tests and proposals for semi-automatic refactoring, there are no studies related to the automatic removal of TS from the test repository. In this context, this study presents a method for automatic TS removal called Eager Test, which occurs when a test verifies more than one method of the code. The proposed method was evaluated through experiments, comparing the original version of a unit tests repository with its automatically refactored version. The results are promising, showing an Eager Test removal rate of 99,4% of unit tests in the repository without causing test errors or test fails. However, there was an increase in test execution time and of lines of code, resulting from the quantity of tests that were extracted. The proposed method supports improving the quality of unit tests and reduces the effort required by developers to remove Eager Test.

Palavras-chave: Test smell, Eager Test, Refactoring, Identification