Test-driven development: Difference between revisions

Revision as of 17:36, 24 July 2004

Revision as of 17:39, 24 July 2004

Line 7:

== Test-Driven Development Cycle ==

=== 1. Write the test ===

It first begins with writing a test. In order to write a test, the specification and requirements must be clearly understood. The next step is to make the test pass by writing the code. This step forces the programmer to take the perspective of a client by seeing the code through it's interfaces. This is the design driven part of TDD. The next step is to run the automated testcases and observe if they pass or fail. If they pass, the programmer can be guaranteed that the code meets the testcases written. If there are failures, the code did not meet the testcases. The final step is the [[refactoring]] step and any code clean-up necessary will occur here. The testcases are then re-run and observed. The cycle will then repeat itself and start with either adding additional functionality or fixing any errors.

It first begins with writing a test. In order to write a test, the specification and requirements must be clearly understood.

=== 2. Write the code ===

The next step is to make the test pass by writing the code. This step forces the programmer to take the perspective of a client by seeing the code through it's interfaces. This is the design driven part of TDD.

=== 3. Run the automated tests ===

The next step is to run the automated testcases and observe if they pass or fail. If they pass, the programmer can be guaranteed that the code meets the testcases written. If there are failures, the code did not meet the testcases.

=== 4. Refactor ===

The final step is the [[refactoring]] step and any code clean-up necessary will occur here. The testcases are then re-run and observed.

=== 5. Repeat ===

The cycle will then repeat itself and start with either adding additional functionality or fixing any errors.

== Differing styles ==