CHAPTER 15 Test-Driven Development
How many times have you programmed and implemented a solution, and then heard from your users that your solution didn’t exactly solve their problems? This is actually very common. So common, in fact, that we almost expect to create multiple solutions for each business problem.
Using the traditional software engineering/architecture approach, we gather requirements, design a solution, and then code that solution. Often, the final product bears little resemblance to the design. Even if the solution produced by this process satisfies the gathered requirements, we find that we misunderstood the requirements. This type of software development reminds me of the famous tree swing diagram, illustrating the disparity ...
Get PeopleSoft PeopleTools Tips & Techniques now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
