The first chapter talks about unit testing. This reiterates the idea of testing early and piece be piece. It is important to do so as the success of the project and customer satisfaction greatly depends on it. The second chapter goes a little bit deeper by emphasizing the writing of little tests first to pace yourself and see where you stand. This makes for more communicative and expressive code. The last chapter discusses releases and getting those changes out. Some of these changes could take some time because of conflicting edits and some are lost all together. IT is important to keep track of all changes and releases. This can be done by avoiding simultaneously editing items.
Dicussion:
I enjoyed in particular the last chapter because I felt the other two were just restating what has been said before about testing early and frequently. This last chapter discussed how to avoid pitfalls one could run into when releasing code. It is helpful to have these in mind.
No comments:
Post a Comment