- 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.
- JavaScript前端開發模塊化教程
- JSP網絡編程(學習筆記)
- Spring 5.0 By Example
- 案例式C語言程序設計
- PyQt從入門到精通
- 深入實踐Spring Boot
- JIRA 7 Administration Cookbook(Second Edition)
- Hadoop+Spark大數據分析實戰
- Mastering Apache Spark 2.x(Second Edition)
- Scratch趣味編程:陪孩子像搭積木一樣學編程
- Flink技術內幕:架構設計與實現原理
- Qt 4開發實踐
- Java RESTful Web Service實戰
- The Applied Data Science Workshop
- LibGDX Game Development By Example