WHAT'S IN THIS CHAPTER?
Application development efforts do not live in a vacuum. The increasing popularity of agile project methodologies is testament to that fact. Even in an agile environment, most development efforts span months — if not years — between the time the first requirement is documented and the day the application is deployed to production. That leaves a lot of time for requirements to change.
Change doesn't end after an application reaches production. No matter how good a job the development team and QA department do, most applications have some sort of defect that isn't discovered until the application reaches production. Even if an application makes it to production and no defects are found, actions and influences from a variety of external forces (customer, government, market forces) can demonstrate a need for changes in an application.
In TDD, defects and new requirements represent opportunities to create new tests. By approaching defects and new requirements with a test-first philosophy, you can more easily deliver a quality application without damaging existing functionality. Reading this book has helped you acquire ...