Skip to Content

Changes for page TDD Workflow Example

Last modified by chrisby on 2023/12/08 07:51
From version 1.7
edited by chrisby
on 2023/12/08 07:46
Change comment: There is no comment for this version
To version 1.6
edited by chrisby
on 2023/12/08 07:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  ### The Role of Git
6 6  
7 -The goal of TDD is to take many small, simple, and safe steps iteratively. A save step, meaning all tests pass, should be physically saved to provide the ability to compare current changes to the last safe step, or to roll back. If something goes wrong, the last safe step is not far away, and finding the problem in a small snippet of changed code makes debugging much easier.
7 +The goal of TDD is to take many small, simple, and safe steps iteratively. A save step, meaning all tests pass, should be physically saved to provide the ability to roll back. Whenever something goes wrong, the last save step is not far away, and rolling back is cheap because only an insignificant amount of code and effort is thrown away.
8 8  
9 9  * When a test passes, **stage the changes** via `git add .`
10 10  * When a test passes and is complete, **commit the staged changes** via `git commit -am "..."`