From 73805b3e0e947abb407da40efab0daf9c4e187dd Mon Sep 17 00:00:00 2001 From: Robert Osborne Date: Sat, 27 Jun 2009 19:21:02 -0400 Subject: [PATCH] re-wrote a bit of explanation of red/green/refactor --- README.rdoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.rdoc b/README.rdoc index 5fafe07..b85cebf 100644 --- a/README.rdoc +++ b/README.rdoc @@ -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: