Making Program Refactoring Safer
IEEE Software2010Vol. 27(4), pp. 52–57
Citations Over TimeTop 10% of 2010 papers
Abstract
Developers rely on compilation, test suites, and tools to preserve observable behavior during refactoring. However, most refactoring tools don't implement all the preconditions that guarantee refactoring correctness because formally identifying them is cost-prohibitive. Therefore, these tools could perform nonbehavior-preserving transformations. The authors present a tool for improving safety during refactoring that automatically generates a test suite suited for detecting behavioral changes. They used this tool to evaluate seven real case study refactorings (from 3 to 100 KLOC).
Related Papers
- → Embracing the C preprocessor during refactoring(2013)12 cited
- Algebraic Semantics of the C Preprocessor and Correctness of its Refactorings(2006)
- → WCET optimization strategy based on source code refactoring(2017)5 cited
- → Model‐based source code refactoring with interaction and visual cues(2023)1 cited
- Manual Refactorings with Automated Correctness Checks ∗(2016)