Test Driven Development pdf epub mobi txt 电子书下载 2025

☆☆☆☆☆

Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles.

出版者:Addison-Wesley Professional

作者:Kent Beck

出品人:

页数:240

译者:

出版时间:2002-11-18

价格:USD 49.99

装帧:Paperback

isbn号码:9780321146533

丛书系列:

图书标签:

TDD
软件开发
软件工程
编程
计算机
agile
programming
Programming

下载链接在页面底部

facebook linkedin mastodon messenger pinterest reddit telegram twitter viber vkontakte whatsapp 复制链接

想要找书就要到小哈图书下载中心

qciss.net

立刻按 ctrl+D收藏本页

你会得到大惊喜!!

Quite simply, test-driven development is meant to eliminate fear in application development. While some fear is healthy (often viewed as a conscience that tells programmers to "be careful!"), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who are unable to absorb constructive criticism. When programming teams buy into TDD, they immediately see positive results. They eliminate the fear involved in their jobs, and are better equipped to tackle the difficult challenges that face them. TDD eliminates tentative traits, it teaches programmers to communicate, and it encourages team members to seek out criticism However, even the author admits that grumpiness must be worked out individually! In short, the premise behind TDD is that code should be continually tested and refactored. Kent Beck teaches programmers by example, so they can painlessly and dramatically increase the quality of their work.

具体描述

读后感

评分☆☆☆☆☆

最近开发了两周的项目上线了（对，又是开源项目改吧改吧就上线了）开发任务突然没有了，而我，每天却要写日报，所以我又想起了多年前的愿望，试一试怎么写测试。这样日报也有的写，还可以提高项目的单元测试率，面试的时候还能说为一个开源项目提供过commit，美滋滋...

评分☆☆☆☆☆

连PhD都能直译成"哲学博士"...google翻译都不会犯这样的错误,失望其它的就不多说了生硬的词语, 不通畅的语句, 费解! 怎么能对的起Kent大神的好书啊!!

评分☆☆☆☆☆

思想很好，传统开发模式下顾问、项目经理管需求，资深开发者、设计者进行分析设计，程序员负责开发，一方面带来项目管理、项目风险诸多问题，另一方面也造就大量"不负责任"的程序员，妨碍程序员综合能力的提升、思维和视角的拓展。TDD下程序员直接面对需求、用例，参与设计，以...

评分☆☆☆☆☆

If I get stuck and I don’t know how a complex algorithm should work I’ll write a test for an error case. Then I’ll write a test for the simplest non-error case I can think of and return a hard coded value. Then I’ll write another test case and see if I ...