The phrase "automated refactoring" is correct and usable in written English.
It can be used in the context of software development, specifically when discussing the process of automatically restructuring existing computer code without changing its external behavior.
Example: "The new tool offers automated refactoring, allowing developers to improve code quality with minimal manual intervention."
Alternatives: "automatic code restructuring" or "automated code improvement".
Therefore, framing object-oriented automated refactoring as a search-based technique has been proposed.
The plugin would then use automated refactoring to help remove the anti-patterns and improve the design of the code.
His research interests include search-based software engineering, software maintenance, automated refactoring and multi-objective search techniques.
Ghaith and Ó Cinnéide (2012) investigated a set of security metrics to determine how successful they could be for improving a security sensitive application using automated refactoring.
CODe-Imp (Moghadam & Cinnéide, 2011) 2011 Automated refactoring tool containing numerous metrics and refactorings.
Tools exist that specifically support different functions for dealing with cross-language links, such as highlighting, error marking, or even automated rename refactoring.
In this paper, four different refactoring approaches are compared using an automated software refactoring tool.
Search-based refactoring to automate software maintenance has been shown to work for experimental examples and various tools have been developed to tackle the maintenance issue using automated means, but more work needs to be done to measure empirical examples.
Software engineering and software re-engineering rely on such transformations, which are automated in, for example, tools for refactoring, migration, program specialisation, compiler optimisation, database re-engineering, software configuration, business-rule extraction, aspect weaving, aspect mining, architectural modifications, and model-driven approaches.
In an Agile environment where the code constantly changes, automated test cases become obsolete and must constantly be refactored in order to provide meaningful feedback about the system's quality.
