Which of the following are true of refactoring (select all that apply)?
OPTIONS:
Refactoring should always introduce new functionality to a code base.
Refactoring does not introduce new end-user features.
Refactoring should not be performed to enhance code modularity.
Refactoring should never be done in conjunction with regression testing.
Answers
Answered by
1
AnsRefactoring should always introduce new functionality to a code base.wer:
Explanation:
Answered by
0
Option a) Refactoring should always introduce new functionality to a code base.
- Refactoring aims to enhance the software's non-functional attributes—its design, structure, and/or implementation—while maintaining its functionality.
- As was previously said, the ideal approach to restructure is to do it gradually. Additionally, it is crucial to perform it before including any new features or functionality in the solution. Refactoring the code shouldn't alter how the product functions in any way.
- Refactoring entails altering the internal organisation of the code without changing its behaviour. As a result, the code is simpler to comprehend and maintain. It helps the team's engineers to maintain control over complexity.
- If you refactor your programme properly, you'll increase its efficiency now and prolong its useful life. Your (future) code will therefore require less work to stay current when habits change and new techniques are created, saving you and your developers time.
#SPJ2
Similar questions