Test-driven development was first introduced as part of the extreme programming (XP) paradigm. While not everyone agrees with all aspects of XP, most developers believe in the benefits of test-driven development. Although the basic techniques of test-driven development are simple to understand, its
Test-driven development by example
✍ Scribed by Kent Beck
- Book ID
- 127398312
- Publisher
- Addison-Wesley Professional
- Year
- 2002
- Tongue
- English
- Weight
- 382 KB
- Series
- Addison-Wesley Signature Series
- Category
- Library
- ISBN-13
- 9780321146533
No coin nor oath required. For personal study only.
✦ Synopsis
Clean code that works - now. This is the seeming contradiction that lies behind much of the pain of programming. Test-driven development replies to this contradiction with a paradox-test the program before you write it. A new idea? Not at all. Since the dawn of computing, programmers have been specifying the inputs and outputs before programming precisely. Test-driven development takes this age-old idea, mixes it with modern languages and programming environments, and cooks up a tasty stew guaranteed to satisfy your appetite for clean code that works-now.Developers face complex programming challenges every day, yet they are not always readily prepared to determine the best solution. More often than not, such difficult projects generate a great deal of stress and bad code. To garner the strength and courage needed to surmount seemingly Herculean tasks, programmers should look to test-driven development (TDD), a proven set of techniques that encourage simple designs and test suites that inspire confidence. By driving development with automated tests and then eliminating duplication, any developer can write reliable, bug-free code no matter what its level of complexity. Moreover, TDD encourages programmers to learn quickly, communicate more clearly, and seek out constructive feedback.
✦ Subjects
Технология программирования
📜 SIMILAR VOLUMES