Navigation

Introduction

The Traditional Waterfall Approach

Agile Methodologies

Conclusion- Choosing the Right Approach for the Task

Bibliography

Test-Driven Development

Figure 8: A possible downside to Test Driven Development

Test-Driven Development

(theserverside.net, n.d.)

Test-Driven Development, as its name implies, is derived from a programmer writing tests first, and then writing code. As the tests are written first, they fail until proper code is applied to them. Once the appropriate code is written, the test passes, and the next test is written. If the code as written does not pass the test, then it is adjusted until the test is passed (Grenning, 2007). An example of this process is shown in Figure 9, below.

Figure 9:

Test Driven Development

(wikipedia.org, n.d.)

Much like the other agile processes that I have mentioned, with Test-Driven Development (TDD), jobs are broken up into small subsets that can be implemented in a short period of time. Code is developed through rapid iterations of minute-by-minute cycles and per-task cycles. The minute-by minute cycles consist of the following:

The per-task cycles are as follows:

Some of the possible benefits of TDD include: