TerribleDev/ruby_koans
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

re-wrote a bit of explanation of red/green/refactor

Browse Source
This commit is contained in:
Robert Osborne
2009-06-27 19:21:02 -04:00
committed by Marc Peabody
parent e225b1612c
commit 73805b3e0e
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.rdoc
View File

@@ -59,8 +59,9 @@ Windows is the same thing
In test-driven development the mantra has always been, red, green, refactor. Write a
failing test and run it (red), make the test pass (green), then refactor it (that is
look at the code and see if you can make it any better. In this case you will need
to run the koan and see it fail (refactor), make the test pass (green), then take a
moment and reflect upon the test to see what it is teaching you.
to run the koan and see it fail (red), make the test pass (green), then take a
moment and reflect upon the test to see what it is teaching you and improve the
code to better communicate its intent (refactor).
The very first time you run it you will see the following output: