- Test-Driven Java Development(Second Edition)
- Alex Garcia Viktor Farcic
- 145字
- 2021-06-24 18:31:45
No debugging
We (authors of this book) almost never debug applications we're working on!
This statement might sound pompous, but it's true. We almost never debug because there is rarely a reason to debug an application. When tests are written before the code and the code coverage is high, we can have high confidence that the application works as expected. This does not mean that applications written using TDD do not have bugs—they do. All applications do. However, when that happens, it is easy to isolate them by simply looking for the code that is not covered by tests.
Tests themselves might not include some cases. In those situations, the action is to write additional tests.
With high code coverage, finding the cause of some bug is much faster through tests than spending time debugging line by line until the culprit is found.
推薦閱讀
- What's New in TensorFlow 2.0
- Vue.js 2 and Bootstrap 4 Web Development
- SAS數(shù)據(jù)統(tǒng)計(jì)分析與編程實(shí)踐
- PLC編程及應(yīng)用實(shí)戰(zhàn)
- 批調(diào)度與網(wǎng)絡(luò)問(wèn)題的組合算法
- Geospatial Development By Example with Python
- Mastering Gephi Network Visualization
- Software-Defined Networking with OpenFlow(Second Edition)
- 深入淺出 HTTPS:從原理到實(shí)戰(zhàn)
- SFML Game Development
- SQL Server 2008實(shí)用教程(第3版)
- 用Python動(dòng)手學(xué)統(tǒng)計(jì)學(xué)
- Swift Essentials(Second Edition)
- Cinder:Begin Creative Coding
- Azure for Architects