Changes for page Test-Driven Development

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,4 +1,4 @@
1		-Before writing the production code, developers write automated tests that should pass once the production code is implemented.
	1	+Before writing the production code, developers write automated tests that should pass once the production code is implemented. You can find a concrete example workflow that includes TDD and versioning with git [[here|path:/bin/view/Software%20Engineering/Agile/Extreme%20Programming/Test-Driven%20Development/TDD%20Workflow%20Example/]].
2	2
3	3	### Benefits
4	4
...	...	@@ -14,7 +14,7 @@
14	14	1. Write only enough of a test to demonstrate a failure.
15	15	1. Write only enough production code to pass the test.
16	16
17		-**Remarks**
	17	+Remarks:
18	18
19	19	* **Not compiling is a failure**: For example, if the test code requires a function from the production code that has not yet been defined, compilation will fail. Since the test fails, you must next go to the production code and make the test pass.
20	20	* **Workflow**: In practice, you start writing a test until it fails, then switch to production until it passes, switch back to test code until it fails, and so on until the feature is complete. This leads to a very fast oscillation of switching between test code and production code. Run tests on the code you are working on at least every few minutes.
...	...	@@ -36,5 +36,3 @@
36	36	1. Implement production code to pass the test. (green terminal output)
37	37	1. Refactor and make sure the tests still pass.
38	38	1. Repeat until done.
39		-
40		-A more complex workflow that includes TDD and versioning with git can be found [[here|path:/bin/view/Software%20Engineering/Agile/Extreme%20Programming/Test-Driven%20Development/TDD%20Workflow%20Example/]].