Refactoring test code

424 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Accurate and Efficient Refactoring Detection in Commit History (2018, background): “, see the case of extensive unit test renames in project cassandra [10]), where developers tend to copy-and-modify older unit tests to create new ones [72], and thus several methods share very similar statements with each other.”
A survey of software refactoring (2004, background): “Van Deursen et al. [108] show that refactoring of test code is different from refactoring production code in two ways: 1) There is a distinct set of bad smells involved and 2) improving test code involves additional test-specific refactorings.”
Java quality assurance by detecting code smells (2002, background): “For example, in an earlier paper, we have identified a number of smells that can occur in unit test code and described the corresponding refactorings to remove them [8].”
Reinforcement Learning from Automatic Feedback for High-Quality Unit Test Generation (2023, unknown): “We found that validation was critical to avoid mode collapse [8] highlights a limitation of filtering-based SFT – properties with low frequency or few co-occurrences restricted the size of the golden training dataset.”