CSC/ECE 517 Fall 2012/ch2a 2w11 aa: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
Danielle | Danielle | ||
=References= | =References= | ||
*[http://catalog.lib.ncsu.edu/record/NCSU1601963 Beck, K. (2002). Test-driven development by example. Addison-Wesley.] | |||
*[http://en.wikipedia.org/wiki/Test_driven_development (n.d.). Test-driven development. website: http://en.wikipedia.org/wiki/Test_driven_development] | |||
*[http://c2.com/cgi/wiki?TestDrivenDevelopment (2012, January 11). Test driven development. website: http://c2.com/cgi/wiki?TestDrivenDevelopment] | |||
*[http://www.agiledata.org/essays/tdd.html Ambler, S. W. (2002). Introduction to test driven development (tdd). Retrieved from Agile Data website: http://www.agiledata.org/essays/tdd.html] | |||
*http://www.testdriven.com/ ? | |||
Revision as of 14:08, 22 October 2012
Introduction
Test driven development (TDD) is a process that tries to create the minimal amount of code to meet customer's expectations. The idea is to test first, code second, then improve (or refactor) last. This process forces the software developers to focus on customer specifications and validation first. Since at each step of the way the programmer proves to himself that the code meets specifications, TDD gives the programmer confidence. The rest of this chapter gives the motivation for TDD, shows the steps for TDD, outlines the principles of TDD, and provides examples using TDD.
Motivation for TDD
Annice
Steps
Annice
Principles
Annice
Examples
Danielle
Conclusion
Danielle
References
- Beck, K. (2002). Test-driven development by example. Addison-Wesley.
- (n.d.). Test-driven development. website: http://en.wikipedia.org/wiki/Test_driven_development
- (2012, January 11). Test driven development. website: http://c2.com/cgi/wiki?TestDrivenDevelopment
- Ambler, S. W. (2002). Introduction to test driven development (tdd). Retrieved from Agile Data website: http://www.agiledata.org/essays/tdd.html
- http://www.testdriven.com/ ?