Java extreme programming cookbook [extreme programming in the real world

Extreme Programming does not mean programming naked while rollerblading down the side of the Grand Canyon. It does mean a new approach to software development that is both radical and common-sense. Unlike many software development methodologies, XP has been accepted quickly because its core practices--particularly code sharing, test-first development, and continuous integration--resonated immediately with software developers everywhere. Instead of impressing developers with a body of theory, XP got programmers to say, "Yeah, that's how I'd like to work."Oddly enough, although most developers turn to Extreme Programming methods in order to code real, hands-on, and extensible projects quickly ("Code comes first"), most books on Extreme Programming insist on focusing on the theory and not the practice.Not the __Java Extreme Programming Cookbook__.Brimming with over 100 "recipes" for getting down to business and actually doing XP, the __Java Extreme Programming Cookbook__ doesn't try to "sell" you on XP; it succinctly documents the most important features of popular open source tools for XP in Java--including Ant, Junit, HttpUnit, Cactus, Tomcat, XDoclet--and then digs right in, providing recipes for implementing the tools in real-world environments.Each recipe offers solutions that help you put an extreme programming environment together: then provides code for automating the build process and testing. Although the time saved using any one of these solutions will more than pay for the book, __Java Extreme Programming Cookbook__ offers more than just a collection of cut-and-paste code. Each recipe also includes explanations of how and why the approach works, so you can adapt the techniques to similar situations.One of the biggest challenges facing developers today is sorting through the wide variety of tools available form various source and figuring out how to them effectively. The recipes in __Java Extreme Programming Cookbook__ showcase how to use the most important features of these XP tools. Many of these tools are geared towards unit testing, while others are invaluable for continuous integration; with these practical examples, you'll be able to choose the most effective tools to accomplish your goals, then implement them in a cohesive development environment quickly.If you want to set up a test-driven development environment that allows you to focus on writing testable code--now--this book will prove invaluable. \*\* JavaTM Extreme Programming Cookbook 1 Copyright 4 Dedication 5 Preface 5 Audience 5 About the Recipes 5 Organization 6 Conventions Used in This Book 7 Comments and Questions 7 Acknowledgments 8 Chapter 1. XP Tools 8 1.1 Java and XP 8 1.2 Tools and Philosophies 9 1.2.1 The IDE Philosophy 9 1.2.2 Minimum Tool Requirements 10 1.2.2.1 Automation 10 1.2.2.2 Regression testing 10 1.2.2.3 Consistency among developers 11 1.3 Open Source Toolkit 11 1.3.1 Version Control 11 1.3.2 Ant 12 1.3.3 JUnit 13 1.3.4 HttpUnit and Cactus 14 1.3.5 JUnitPerf 15 1.3.6 Application Servers 15 1.3.7 Setting Up a Build Server 15 Chapter 2. XP Overview 16 2.1 What Is XP? 16 2.1.1 Simplicity 16 2.1.2 Communication 17 2.1.3 Feedback 18 2.1.4 Courage 18 2.2 Coding 18 2.2.1 Simplicity 19 2.2.2 Comments 19 2.2.3 Pair Programming 20 2.2.4 Collective Code Ownership 20 2.2.5 Coding Standards 21 2.2.6 Code Inspections 21 2.3 Unit Testing 22 2.3.1 Why Test? 22 2.3.2 Who Writes Unit Tests? 22 2.3.3 What Tests Are Written? 22 2.3.4 Testing New Features 23 2.3.5 Testing Bugs 23 2.3.6 How Do You Write Tests? 24 2.3.7 Unit Tests Always Pass 24 2.3.8 Testing Improves Design 24 2.3.9 Acceptance Testing 25 2.4 Refactoring 25 2.4.1 Goals 26 2.4.2 When to Refactor 26 2.4.3 How to Refactor 27 2.4.4 Refactoring Tools 27 2.5 Design 27 2.5.1 Design Today's Features 27 2.5.2 Simple Design 28 2.5.3 UML 28 2.5.3.1 UML tools 28 2.5.3.2 Whiteboards and scratch paper 29 2.6 Builds 29 2.6.1 Continuous Integration 29 2.6.2 Small Tasks 30 Chapter 3. Ant 30 3.1 Introduction 31 3.2 Writing a Basic Buildfile 31 3.2.1 Problem 31 3.2.2 Solution 32 3.2.3 Discussion 32 3.2.4 See Also 33 3.3 Running Ant 34 3.3.1 Problem 34 3.3.2 Solution 34 3.3.3 Discussion 34 3.3.4 See Also 35 3.4 Providing Help 35 3.4.1 Problem 35 3.4.2 Solution 35 3.4.3 Discussion 35 3.4.4 See Also 36 3.5 Using Environment Variables 37 3.5.1 Problem 37 3.5.2 Solution 37 3.5.3 Discussion 37 3.5.4 See Also 38 3.6 Passing Arguments to a Buildfile 38 3.6.1 Problem 38 3.6.2 Solution 38 3.6.3 Discussion 39 3.6.4 See Also 41 3.7 Checking for the Existence of Properties 41 3.7.1 Problem 42 3.7.2 Solution 42 3.7.3 Discussion 42 3.7.4 See Also 42 3.8 Defining a Classpath 42 3.8.1 Problem 42 3.8.2 Solution 42 3.8.3 Discussion 43 3.8.4 See Also 45 3.9 Defining Platform-Independent Paths 45 3.9.1 Problem 45 3.9.2 Solution 45 3.9.3 Discussion 45 3.9.4 See Also 45 3.10 Including and Excluding Files 45 3.10.1 Problem 46 3.10.2 Solution 46 3.10.3 Discussion 46 3.10.4 See Also 46 3.11 Implementing Conditional Logic 47 3.11.1 Problem 47 3.11.2 Solution 47 3.11.3 Discussion 47 3.11.4 See Also 47 3.12 Defining a Consistent Environment 47 3.12.1 Problem 47 3.12.2 Solution 47 3.12.3 Discussion 48 3.12.4 See Also 48 3.13 Preventing Build Breaks 48 3.13.1 Problem 48 3.13.2 Solution 48 3.13.3 Discussion 48 3.13.4 See Also 49 3.14 Building JAR Files 49 3.14.1 Problem 49 3.14.2 Solution 49 3.14.3 Discussion 49 3.14.4 See Also 50 3.15 Installing JUnit 50 3.15.1 Problem 50 3.15.2 Solution 50 3.15.3 Discussion 50 3.15.4 See Also 52 3.16 Running Unit Tests 52 3.16.1 Problem 52 3.16.2 Solution 52 3.16.3 Discussion 53 3.16.4 See Also 55 3.17 Running Specific Tests 55 3.17.1 Problem 55 3.17.2 Solution 56 3.17.3 Discussion 56 3.17.4 See Also 56 3.18 Generating a Test Report 56 3.18.1 Problem 56 3.18.2 Solution 56 3.18.3 Discussion 57 3.18.4 See Also 58 3.19 Checking Out Code from CVS 58 3.19.1 Problem 58 3.19.2 Solution 58 3.19.3 Discussion 58 3.19.4 See Also 59 3.20 Bootstrapping a Build 59 3.20.1 Problem 59 3.20.2 Solution 59 3.20.3 Discussion 59 3.20.4 See Also 60 Chapter 4. JUnit 60 4.1 Introduction 61 4.2 Getting Started 62 4.2.1 Problem 62 4.2.2 Solution 62 4.2.3 Discussion 62 4.2.4 See Also 64 4.3 Running JUnit 64 4.3.1 Problem 64 4.3.2 Solution 64 4.3.3 Discussion 64 4.3.3.1 Text testing 64 4.3.3.2 Graphical testing 66 4.3.3.3 Reload classes every run 68 4.3.4 See Also 68 4.4 assertXXX( ) Methods 68 4.4.1 Problem 68 4.4.2 Solution 68 4.4.3 Discussion 68 4.4.3.1 Optional first argument 69 4.4.3.2 Equality comparison 69 4.4.3.3 Additional examples 70 4.4.4 See Also 71 4.5 Unit Test Granularity 71 4.5.1 Problem 71 4.5.2 Solution 71 4.5.3 Discussion 71 4.5.4 See Also 72 4.6 Set Up and Tear Down 73 4.6.1 Problem 73 4.6.2 Solution 73 4.6.3 Discussion 73 4.6.4 See Also 74 4.7 One-Time Set Up and Tear Down 74 4.7.1 Problem 74 4.7.2 Solution 75 4.7.3 Discussion 75 4.7.4 See Also 76 4.8 Organizing Tests into Test Suites 76 4.8.1 Problem 76 4.8.2 Solution 76 4.8.3 Discussion 76 4.8.4 See Also 77 4.9 Running a Test Class Directly 77 4.9.1 Problem 77 4.9.2 Solution 77 4.9.3 Discussion 78 4.9.4 See Also 78 4.10 Repeating Tests 78 4.10.1 Problem 78 4.10.2 Solution 78 4.10.3 Discussion 78 4.10.4 See Also 79 4.11 Test Naming Conventions 79 4.11.1 Problem 79 4.11.2 Solution 79 4.11.3 Discussion 79 4.11.4 See Also 80 4.12 Unit Test Organization 80 4.12.1 Problem 80 4.12.2 Solution 80 4.12.3 Discussion 81 4.12.4 See Also 82 4.13 Exception Handling 82 4.13.1 Problem 82 4.13.2 Solution 82 4.13.3 Discussion 83 4.14 Running Tests Concurrently 83 4.14.1 Problem 84 4.14.2 Solution 84 4.14.3 Discussion 84 4.14.4 See Also 85 4.15 Testing Asynchronous Methods 85 4.15.1 Problem 85 4.15.2 Solution 85 4.15.3 Discussion 85 4.15.4 See Also 87 4.16 Writing a Base Class for Your Tests 87 4.16.1 Problem 87 4.16.2 Solution 87 4.16.3 Discussion 88 4.17 Testing Swing Code 88 4.17.1 Problem 88 4.17.2 Solution 88 4.17.3 Discussion 89 4.17.4 See Also 93 4.18 Avoiding Swing Threading Problems 93 4.18.1 Problem 93 4.18.2 Solution 93 4.18.3 Discussion 93 4.18.4 See Also 96 4.19 Testing with the Robot 96 4.19.1 Problem 96 4.19.2 Solution 96 4.19.3 Discussion 96 4.19.4 See Also 96 4.20 Testing Database Logic 96 4.20.1 Problem 97 4.20.2 Solution 97 4.20.3 Discussion 97 4.20.4 See Also 98 4.21 Repeatedly Testing the Same Method 98 4.21.1 Problem 98 4.21.2 Solution 98 4.21.3 Discussion 98 4.21.4 See Also 102 Chapter 5. HttpUnit 102 5.1 Introduction 103 5.2 Installing HttpUnit 103 5.2.1 Problem 103 5.2.2 Solution 104 5.2.3 Discussion 104 5.2.4 See Also 104 5.3 Preparing for Test-First Development 104 5.3.1 Problem 104 5.3.2 Solution 104 5.3.3 Discussion 104 5.3.4 See Also 108 5.4 Checking a Static Web Page 108 5.4.1 Problem 108 5.4.2 Solution 108 5.4.3 Discussion 108 5.4.4 See Also 109 5.5 Following Hyperlinks 109 5.5.1 Problem 110 5.5.2 Solution 110 5.5.3 Discussion 110 5.5.4 See Also 111 5.6 Writing Testable HTML 111 5.6.1 Problem 111 5.6.2 Solution 111 5.6.3 Discussion 111 5.6.4 See Also 112 5.7 Testing HTML Tables 112 5.7.1 Problem 112 5.7.2 Solution 112 5.7.3 Discussion 112 5.7.4 See Also 115 5.8 Testing a Form Tag and Refactoring Your Tests 115 5.8.1 Problem 115 5.8.2 Solution 115 5.8.3 Discussion 115 5.9 Testing for Elements on HTML Forms 118 5.9.1 Problem 118 5.9.2 Solution 118 5.9.3 Discussion 118 5.9.4 See Also 120 5.10 Submitting Form Data 120 5.10.1 Problem 120 5.10.2 Solution 120 5.10.3 Discussion 121 5.10.4 See Also 124 5.11 Testing Through a Firewall 124 5.11.1 Problem 124 5.11.2 Solution 124 5.11.3 Discussion 124 5.11.4 See Also 124 5.12 Testing Cookies 125 5.12.1 Problem 125 5.12.2 Solution 125 5.12.3 Discussion 125 5.12.4 See Also 126 5.13 Testing Secure Pages 126 5.13.1 Problem 127 5.13.2 Solution 127 5.13.3 Discussion 127 5.13.4 See Also 127 Chapter 6. Mock Objects 128 6.1 Introduction 128 6.2 Event Listener Testing 129 6.2.1 Problem 129 6.2.2 Solution 129 6.2.3 Discussion 129 6.2.4 See Also 134 6.3 Mock Object Self-Validation 134 6.3.1 Problem 134 6.3.2 Solution 134 6.3.3 Discussion 134 6.3.4 See Also 137 6.4 Writing Testable JDBC Code 137 6.4.1 Problem 137 6.4.2 Solution 137 6.4.3 Discussion 137 6.4.4 See Also 139 6.5 Testing JDBC Code 140 6.5.1 Problem 140 6.5.2 Solution 140 6.5.3 Discussion 140 6.5.4 See Also 143 6.6 Generating Mock Objects with MockMaker 143 6.6.1 Problem 143 6.6.2 Solution 143 6.6.3 Discussion 143 6.6.4 See Also 144 6.7 Breaking Up Methods to Avoid Mock Objects 145 6.7.1 Problem 145 6.7.2 Solution 145 6.7.3 Discussion 145 6.7.4 See Also 146 6.8 Testing Server-Side Business Logic 146 6.8.1 Problem 146 6.8.2 Solution 146 6.8.3 Discussion 147 6.8.4 See Also 148 Chapter 7. Cactus 149 7.1 Introduction 149 7.1.1 Implicit Objects 150 7.1.2 How Does It Work? 150 7.2 Configuring Cactus 152 7.2.1 Problem 152 7.2.2 Solution 152 7.2.3 Discussion 152 7.2.3.1 Client-side classpath 152 7.2.3.2 Server-side classpath 153 7.2.4 See Also 153 7.3 Setting Up a Stable Build Environment 154 7.3.1 Problem 154 7.3.2 Solution 154 7.3.3 Discussion 154 7.3.4 See Also 160 7.4 Creating the cactus.properties File 160 7.4.1 Problem 160 7.4.2 Solution 161 7.4.3 Discussion 161 7.4.4 See Also 162 7.5 Generating the cactus.properties File Automatically 162 7.5.1 Problem 162 7.5.2 Solution 162 7.5.3 Discussion 163 7.5.4 See Also 164 7.6 Writing a Cactus Test 164 7.6.1 Problem 164 7.6.2 Solution 164 7.6.3 Discussion 164 7.6.4 See Also 167 7.7 Submitting Form Data 167 7.7.1 Problem 167 7.7.2 Solution 167 7.7.3 Discussion 168 7.7.4 See Also 172 7.8 Testing Cookies 172 7.8.1 Problem 173 7.8.2 Solution 173 7.8.3 Discussion 173 7.8.3.1 testGetInitialCookie( ) 174 7.8.3.2 testGetUpdatedCookie( ) 174 7.8.4 See Also 176 7.9 Testing Session Tracking Using HttpSession 176 7.9.1 Problem 176 7.9.2 Solution 176 7.9.3 Discussion 176 7.9.4 See Also 182 7.10 Testing Servlet Initialization Parameters 182 7.10.1 Problem 182 7.10.2 Solution 182 7.10.3 Discussion 182 7.10.4 See Also 183 7.11 Testing Servlet Filters 183 7.11.1 Problem 183 7.11.2 Solution 183 7.11.3 Discussion 184 7.11.4 See Also 187 7.12 Securing Cactus Tests 187 7.12.1 Problem 187 7.12.2 Solution 187 7.12.3 Discussion 187 7.12.4 See Also 189 7.13 Using HttpUnit to Perform Complex Assertions 189 7.13.1 Problem 189 7.13.2 Solution 189 7.13.3 Discussion 190 7.13.4 See Also 190 7.14 Testing the Output of a JSP 190 7.14.1 Problem 190 7.14.2 Solution 190 7.14.3 Discussion 190 7.14.4 See Also 191 7.15 When Not to Use Cactus 191 7.15.1 Problem 191 7.15.2 Solution 191 7.15.3 Discussion 191 7.15.4 See Also 192 7.16 Designing Testable JSPs 192 7.16.1 Problem 192 7.16.2 Solution 192 7.16.3 Discussion 192 7.16.4 See Also 192 Chapter 8. JUnitPerf 192 8.1 Introduction 193 8.2 When to Use JUnitPerf 194 8.2.1 Problem 194 8.2.2 Solution 194 8.2.3 Discussion 194 8.2.4 See Also 195 8.3 Creating a Timed Test 195 8.3.1 Problem 195 8.3.2 Solution 195 8.3.3 Discussion 195 8.3.4 See Also 198 8.4 Creating a LoadTest 198 8.4.1 Problem 198 8.4.2 Solution 198 8.4.3 Discussion 198 8.4.4 See Also 200 8.5 Creating a Timed Test for Varying Loads 201 8.5.1 Problem 201 8.5.2 Solution 201 8.5.3 Discussion 201 8.5.4 See Also 202 8.6 Testing Individual Response Times Under Load 202 8.6.1 Problem 202 8.6.2 Solution 202 8.6.3 Discussion 202 8.6.4 See Also 203 8.7 Running a TestSuite with Ant 203 8.7.1 Problem 203 8.7.2 Solution 203 8.7.3 Discussion 203 8.8 Generating JUnitPerf Tests 204 8.8.1 Problem 204 8.8.2 Solution 204 8.8.3 Discussion 204 8.8.3.1 Creating a timed test 204 8.8.3.2 Creating a load test 205 8.8.3.3 Generating the code 205 8.8.4 See Also 206 Chapter 9. XDoclet 207 9.1 Introduction 207 9.2 Setting Up a Development Environment for Generated Files 208 9.2.1 Problem 208 9.2.2 Solution 208 9.2.3 Discussion 208 9.2.3.1 Why not place generated files in the source directory? 209 9.2.3.2 Why not place generated files in the build directory? 209 9.2.3.3 Why not place the compiled generated code in the build directory? 210 9.2.4 See Also 210 9.3 Setting Up Ant to Run XDoclet 210 9.3.1 Problem 210 9.3.2 Solution 210 9.3.3 Discussion 210 9.3.4 See Also 213 9.4 Regenerating Files That Have Changed 213 9.4.1 Problem 213 9.4.2 Solution 213 9.4.3 Discussion 213 9.4.4 See Also 214 9.5 Generating the EJB Deployment Descriptor 215 9.5.1 Problem 215 9.5.2 Solution 215 9.5.3 Discussion 215 9.5.4 See Also 218 9.6 Specifying Different EJB Specifications 218 9.6.1 Problem 218 9.6.2 Solution 218 9.6.3 Discussion 218 9.6.4 See Also 219 9.7 Generating EJB Home and Remote Interfaces 219 9.7.1 Problem 219 9.7.2 Solution 219 9.7.3 Discussion 219 9.7.4 See Also 224 9.8 Creating and Executing a Custom Template 224 9.8.1 Problem 224 9.8.2 Solution 224 9.8.3 Discussion 224 9.8.3.1 Block 224 9.8.3.2 Content 225 9.8.4 See Also 227 9.9 Extending XDoclet to Generate Custom Files 227 9.9.1 Problem 227 9.9.2 Solution 227 9.9.3 Discussion 228 9.9.4 See Also 228 9.10 Creating an Ant XDoclet Task 228 9.10.1 Problem 228 9.10.2 Solution 228 9.10.3 Discussion 228 9.10.3.1 Creating an Ant XDoclet task 229 9.10.3.2 Creating the Ant Doclet subtask 230 9.10.4 See Also 233 9.11 Creating an XDoclet Tag Handler 233 9.11.1 Problem 233 9.11.2 Solution 233 9.11.3 Discussion 233 9.11.3.1 Block 234 9.11.3.2 Content 234 9.11.4 See Also 240 9.12 Creating a Template File 240 9.12.1 Problem 240 9.12.2 Solution 240 9.12.3 Discussion 240 9.12.4 See Also 243 9.13 Creating an XDoclet xdoclet.xml File 243 9.13.1 Problem 243 9.13.2 Solution 243 9.13.3 Discussion 243 9.13.4 See Also 245 9.14 Creating an XDoclet Module 245 9.14.1 Problem 245 9.14.2 Solution 245 9.14.3 Discussion 245 9.14.4 See Also 246 Chapter 10. Tomcat and JBoss 246 10.1 Introduction 247 10.2 Managing Web Applications Deployed to Tomcat 247 10.2.1 Problem 247 10.2.2 Solution 247 10.2.3 Discussion 247 10.2.4 See Also 248 10.3 Hot-Deploying to Tomcat 248 10.3.1 Problem 248 10.3.2 Solution 248 10.3.3 Discussion 248 10.3.4 See Also 249 10.4 Removing a Web Application from Tomcat 250 10.4.1 Problem 250 10.4.2 Solution 250 10.4.3 Discussion 250 10.4.4 See Also 251 10.5 Checking If a Web Application Is Deployed 251 10.5.1 Problem 251 10.5.2 Solution 251 10.5.3 Discussion 251 10.5.4 See Also 252 10.6 Starting Tomcat with Ant 252 10.6.1 Problem 252 10.6.2 Solution 252 10.6.3 Discussion 252 10.6.4 See Also 260 10.7 Stopping Tomcat with Ant 260 10.7.1 Problem 260 10.7.2 Solution 260 10.7.3 Discussion 260 10.8 Setting Up Ant to Use Tomcat's Manager Web Application 261 10.8.1 Problem 261 10.8.2 Solution 261 10.8.3 Discussion 261 10.8.4 See Also 262 10.9 Hot-Deploying to JBoss 262 10.9.1 Problem 262 10.9.2 Solution 262 10.9.3 Discussion 263 10.9.4 See Also 264 10.10 Hot-Deploying a Web Application to JBoss 264 10.10.1 Problem 264 10.10.2 Solution 264 10.10.3 Discussion 264 10.10.4 See Also 264 10.11 Testing Against Multiple Servers 264 10.11.1 Problem 264 10.11.2 Solution 264 10.11.3 Discussion 264 10.11.4 See Also 265 Chapter 11. Additional Topics 265 11.1 Introduction 265 11.2 Testing XML Files 265 11.2.1 Problem 265 11.2.2 Solution 265 11.2.3 Discussion 266 11.2.4 See Also 266 11.3 Enterprise JavaBeans Testing Tools 267 11.3.1 Problem 267 11.3.2 Solution 267 11.3.3 Discussion 267 11.3.3.1 ServletTestCase 267 11.3.3.2 J2EEUnit 267 11.3.4 See Also 268 11.4 Avoiding EJB Testing 268 11.4.1 Problem 268 11.4.2 Solution 268 11.4.3 Discussion 268 11.4.4 See Also 269 11.5 Testing Swing GUIs 269 11.5.1 Problem 269 11.5.2 Solution 269 11.5.3 Discussion 269 11.5.3.1 Abbot 270 11.5.3.2 Pounder 270 11.5.3.3 Jemmy 270 11.5.3.4 JFCUnit 270 11.5.4 See Also 271 11.6 Testing Private Methods 271 11.6.1 Problem 271 11.6.2 Solution 271 11.6.3 Discussion 271 11.6.4 See Also 272

Extreme Programming does not mean programming naked while rollerblading down the side of the Grand Canyon. It does mean a new approach to software development that is both radical and common-sense. Unlike many software development methodologies, XP has been accepted quickly because its core practices—particularly code sharing, test-first development, and continuous integration—resonated immediately with software developers everywhere. Instead of impressing developers with a body of theory, XP got programmers to say, "Yeah, that's how I'd like to work."

Oddly enough, although most developers turn to Extreme Programming methods in order to code real, hands-on, and extensible projects quickly ("Code comes first"), most books on Extreme Programming insist on focusing on the theory and not the practice.

Not the Java Extreme Programming Cookbook.

Brimming with over 100 "recipes" for getting down to business and actually doing XP, the Java Extreme Programming Cookbook doesn't try to "sell" you on XP; it succinctly documents the most important features of popular open source tools for XP in Java—including Ant, Junit, HttpUnit, Cactus, Tomcat, XDoclet—and then digs right in, providing recipes for implementing the tools in real-world environments.

Each recipe offers solutions that help you put an extreme programming environment together: then provides code for automating the build process and testing. Although the time saved using any one of these solutions will more than pay for the book, Java Extreme Programming Cookbook offers more than just a collection of cut-and-paste code. Each recipe also includes explanations of how and why the approach works, so you can adapt the techniques to similar situations.

One of the biggest challenges facing developers today is sorting through the wide variety of tools available form various source and figuring out how to them effectively. The recipes in Java Extreme Programming Cookbook showcase how to use the most important features of these XP tools. Many of these tools are geared towards unit testing, while others are invaluable for continuous integration; with these practical examples, you'll be able to choose the most effective tools to accomplish your goals, then implement them in a cohesive development environment quickly.

If you want to set up a test-driven development environment that allows you to focus on writing testable code—now—this book will prove invaluable.

Brimming with over 100 "recipes" for getting down to business and actually doing XP, the Java Extreme Programming Cookbook doesn't try to "sell" you on XP; it succinctly documents the most important features of popular open source tools for XP in Java--including Ant, Junit, Http'nit, Cactus, Tomcat, XDoclet--and then digs right in, providing recipes for implementing the tools in real-world environments.

Extreme Programming does not mean programming naked while rollerblading down the side of the Grand Canyon. It does mean a new approach to software development that is both radical and common-sense. Unlike many software development methodologies, XP has been accepted quickly because its core practices---particularly code sharing, test-first development, and continuous integration---resonated immediately with software developers everywhere. Instead of impressing developers with a body of theory, XP got programmers to say, "Yeah, that's how I'd like to work." Oddly enough, although most developers turn to Extreme Programming methods in order to code real, hands-on, and extensible projects quickly ("Code comes first"), most books on Extreme Programming insist on focusing on the theory and not the practice. Not the Java Extreme Programming Cookbook, brimming with over 100 "recipes" for getting down to business and actually doing XP, the Java Extreme Programming Cookbook doesn't try to "sell" you on XP; it succinctly documents the most important features of popular open source tools for XP in Java---including Ant, Junit, HttpUnit, Cactus, Tomcat, XDoclet---and then digs right in, providing recipes for implementing the tools in real-world environments. Each recipe offers solutions that help you put an extreme programming environment together: then provides code for automating the build process and testing. Although the time saved using any one of these solutions will more than pay for the book, Java Extreme Programming Cookbook offers more than just a collection of cut-and-paste code. Each recipe also includes explanations of how and why the approach works, so you can adapt the techniques to similar situations. One of the biggest challenges facing developers today is sorting through the wide variety of tools available form various sources and figuring out how to them use them effectively. The recipes in Java Extreme Programming Cookbook showcase how to use the most important features of these XP tools. Many of these tools are geared towards unit testing, while others are invaluable for continuous integration; with these practical examples, you'll be able to chose the most effective tools to accomplish your goals, then implement them in a cohesive development environment quickly. Extreme Programming does not mean programming naked while rollerblading down the side of the Grand Canyon. It's a new approach to software development that is both radical and common-sense. Unlike many software development methodologies, XP has been accepted quickly because its core practices -- particularly code sharing, test-first development, and continuous integration -- resonated immediately with software developers everywhere. Instead of impressing developers with a body of theory, XP got programmers to say, "Yeah, that's how I'd like to work." The Java Extreme Programming Cookbook shows how to use the many tools that support extreme programming in Java. Like O'Reilly's other cookbooks, the Java Extreme Programming Cookbook is an extremely practical collection of recipes that show you how to solve common problems. And like XP itself, this book offers a wealth of common-sense advice that helps you become more effective: it shows you how to set up a consistent build environment, do unit testing, test servlets effectively, measure performance, and much more. If you need to jump-start an extreme programming environment, if you've been wanting to investigate XP but haven't known where to start, or if you've implemented an XP environment that isn't quite working to your satisfaction, this book will be invaluable. Brimming with over 100 «recipes» for getting down to business and actually doing XP, the Java Extreme Programming Cookbook doesnt try to «sell» you on XP it succinctly documents the most important features of popular open source tools for XP in Java-- including Ant, Junit, HttpUnit, Cactus, Tomcat, XDoclet-- and then digs right in, providing recipes for implementing the tools in real-world environments. Each recipe offers solutions that help you put an extreme programming environment together: then provides code for automating the build process and testing. Although the time saved using any one of these solutions will more than pay for the book, Java Extreme Programming Cookbook offers more than just a collection of cut-and-paste code. Each recipe also includes explanations of how and why the approach works, so you can adapt the techniques to similar situations.