官术网_书友最值得收藏!

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.

主站蜘蛛池模板: 麟游县| 张家口市| 太白县| 清河县| 久治县| 韶山市| 宁南县| 屏南县| 常山县| 桐乡市| 延川县| 蕉岭县| 昭觉县| 山东| 柘城县| 郯城县| 阿拉善右旗| 莱州市| 和政县| 光山县| 岐山县| 贺兰县| 上高县| 永靖县| 于田县| 育儿| 上犹县| 兴国县| 清水河县| 阳朔县| 田阳县| 平利县| 义乌市| 平湖市| 襄樊市| 成武县| 积石山| 都兰县| 兖州市| 石河子市| 绥棱县|