"Do not let circumstances control you. You change your circumstances."
– Jackie Chan
We have seen so far how TDD makes the development process easier and decreases the amount of time spent on writing quality code. But there's another particular benefit to this. As code is being tested and its correctness is proven, we can go a step further and assume that our code is production-ready once all tests have passed.
There are some software life cycle approaches based on this idea. Some extreme programming (XP) practices such as continuous integration (CI), continuous delivery, and continuous deployment (CD) will be introduced. The code examples can be found at https://bitbucket.org/alexgarcia/packt-tdd-java/src/ ...
