- C# and .NET Core Test Driven Development
- Ayobami Adewole
- 183字
- 2021-06-25 22:00:31
Doing TDD the wrong way
As interesting as practicing TDD can be, it can also be wrongly done. Programmers new to TDD can sometimes write monster tests that are way too large and defeat the purpose of test brevity and being able to perform the TDD cycle quickly, leading to a waste of productive development time.
Partial adoption of the technique can also reduce the full benefit of TDD. In situations where only a few developers in a team use the technique and others don't, this will lead to fragmented code where a portion of code is tested and another portion is not, resulting in an unreliable application.
You should avoid writing tests for code that are naturally trivial or not required; for example, writing tests for object accessors. Tests should be run frequently, especially through the use of test runners, build tools, or continuous integration tools. Failing to run the tests often can lead to a situation where the true reflection of the state of the code base is not known even when changes have been made and components are probably failing.
- Mastering RabbitMQ
- Power Up Your PowToon Studio Project
- PaaS程序設計
- STM32F0實戰:基于HAL庫開發
- 大學計算機基礎實驗指導
- Building Microservices with .NET Core
- Hands-On GUI Programming with C++ and Qt5
- 編寫高質量代碼:改善Objective-C程序的61個建議
- Python Interviews
- 零基礎學HTML+CSS第2版
- Building Scalable Apps with Redis and Node.js
- Python GUI設計tkinter菜鳥編程(增強版)
- Building Microservices with .NET Core 2.0(Second Edition)
- 軟件測試
- 嵌入式Linux與物聯網軟件開發:C語言內核深度解析