-Which is test-first development. The key idea is that any program - -2
-feature that doesn't have an automatic test simply does not exist. If - -3
-there is a feature, you need to write a test for the - -4
-feature before. So, what developers do is to create unit tests for - -5
-each such piece of functionality even before the functionality is implemented. - -6
-And of course, when you run this test, they will fail. But - -7
-the beauty of it is that, as you write your code and - -8
-you add more and more fractionality to the feature that you're developing, - -9
-these test cases are going to start to pass. - -10
-And that's extremely rewarding because it gives you immediate - -11
-feedback, again feedback on the fact that you're - -12
-developing the code in the right way. As soon - -13
-as you write it, you will know. And if you write a piece of code and the - -14
-test says still fail, that means that the - -15
-code is not doing what it's supposed to do. -- cgit 1.4.1