Test-driven development: A J2EE Example

✍ Scribed by Gold R., Hammell T., Snyder T.

Year: 2004
Tongue: English
Leaves: 296
Category: Library

No coin nor oath required. For personal study only.

✦ Synopsis

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 application in the real world requires knowledge of certain tools and techniques needed to effectively create, run and organize tests. This book is targeted at Java developers who want to learn how to use test-driven development to improve the development process for constructing J2EE applications.

📜 SIMILAR VOLUMES

Test Driven Development: By Example

📁 Test Driven Development: By Example

✍ Kent Beck 📂 Library 📅 2002 🏛 Addison-Wesley Professional 🌐 English

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 a

Test-Driven Development By Example

📁 Test-Driven Development By Example

✍ Kent Beck 📂 Library 📅 2002 🏛 Addison Wesley 🌐 English

Test-Driven Development By Example

📁 Test-Driven Development By Example

✍ Kent Beck 📂 Library 📅 2002 🏛 Addison-Wesley Professional 🌐 English

Test Driven Development: By Example

📁 Test Driven Development: By Example

✍ Beck, Kent 📂 Library 📅 2002 🏛 Addison-Wesley Professional; Pearson Education (US 🌐 English

Test Driven Development: By Example

📁 Test Driven Development: By Example

✍ Beck, Kent 📂 Library 📅 2002 🏛 Addison-Wesley Professional; Pearson Education (US 🌐 English

Test-driven development by example

📁 Test-driven development by example

✍ Kent Beck 📂 Library 📅 2002 🏛 Addison-Wesley Professional 🌐 English

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 speci