- Test-Driven Java Development(Second Edition)
- Alex Garcia Viktor Farcic
- 158字
- 2021-06-24 18:31:51
Refactoring
While all the previous steps are mandatory, this one is optional. Even though refactoring is rarely done at the end of each cycle, sooner or later it will be desired, if not mandatory. Not every implementation of a test requires refactoring. There is no rule that tells you when to refactor and when not to. The best time is as soon as one gets a feeling that the code can be rewritten in a better or more optimum way.
What constitutes a candidate for refactoring? This is a hard question to answer since it can have many answers—it's hard to understand code, the illogical location of a piece of code, duplication, names that do not clearly state a purpose, long methods, classes that do too many things, and so on. The list can go on and on. No matter what the reasons are, the most important rule is that refactoring cannot change any existing functionality.
- The Android Game Developer's Handbook
- 微服務設計原理與架構
- 碼上行動:用ChatGPT學會Python編程
- Swift Playgrounds少兒趣編程
- Linux Shell核心編程指南
- JavaScript腳本特效編程給力起飛
- Go語言從入門到精通
- Moodle 3 Administration(Third Edition)
- 奔跑吧 Linux內核
- Java Web開發基礎與案例教程
- 3D Printing Designs:The Sun Puzzle
- Visual C++網絡編程教程(Visual Studio 2010平臺)
- 谷歌JAX深度學習從零開始學
- Neo4j High Performance
- Go語言從入門到項目實戰(視頻版)