Test smells degrade the quality of code and often occur together, indicating the need for combined refactorings to eliminate them. Although existing literature provides evidence of co-occurrences of test smells, little is known about the impact of refactoring such co-occurrences. In this context, it is crucial to understand the potential impact of combining test code refactoring strategies to eliminate multiple instances of test smells. This study reports on the analysis of test code refactoring of an open-source software project. The results indicate some consequences of test code removing concerning test smell co-occurrence: (i) no fixing of test smells; (ii) fixing multiple test smells instances together; and (iii) fixing single test smell instances.