git://git.eng.unimelb.edu.au
/
ruby_koans.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (parent:
7bef325
)
add missing: )
author
Erkan Yilmaz
<erkan77@gmail.com>
Thu, 8 Mar 2012 12:57:01 +0000
(13:57 +0100)
committer
Erkan Yilmaz
<erkan77@gmail.com>
Thu, 8 Mar 2012 12:57:01 +0000
(13:57 +0100)
README.rdoc
patch
|
blob
|
history
diff --git
a/README.rdoc
b/README.rdoc
index
f8208bc
..
75e53a7
100644
(file)
--- a/
README.rdoc
+++ b/
README.rdoc
@@
-71,7
+71,7
@@
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
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
+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 (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).
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).