diff options
| author | Madhusudan.C.S | 2010-07-14 00:19:54 +0530 |
|---|---|---|
| committer | Madhusudan.C.S | 2010-07-14 00:19:54 +0530 |
| commit | d776c870c82fe38eedd78d870ff0a4c3b872129e (patch) | |
| tree | 00d78b3728ffa80ca18a3b54e17bcb8531e6465f /tdd | |
| parent | 5b9768ccc2176a7bb1c7de5eacba27897e98c316 (diff) | |
| download | sees-d776c870c82fe38eedd78d870ff0a4c3b872129e.tar.gz sees-d776c870c82fe38eedd78d870ff0a4c3b872129e.tar.bz2 sees-d776c870c82fe38eedd78d870ff0a4c3b872129e.zip | |
Add a section on real life tests.
Diffstat (limited to 'tdd')
| -rw-r--r-- | tdd/tdd.rst | 10 |
1 files changed, 8 insertions, 2 deletions
diff --git a/tdd/tdd.rst b/tdd/tdd.rst index 9455b67..7044dc6 100644 --- a/tdd/tdd.rst +++ b/tdd/tdd.rst @@ -6,8 +6,8 @@ development which banks on the idea of writing test cases that fail for the code that doesn't even exist yet. The actual code is written later to pass the test and then refactored. -Writing tests -============= +First "Test" +============ Writing a test is simple. Writing a failing test? It is much more simple. Let us consider a very simple program which returns the Greatest Common @@ -76,3 +76,9 @@ tests? So what else should we wait for? Let us write our first test!:: exit(1) print "All tests passed!" + +More realistic "Tests" +====================== + +Now we have completed writing our first test. Let us start writing tests +for more realistic |