Difference between revisions of "Test-driven development"
Jump to navigation
Jump to search
(→Sources: += InfoQ » Scott Ambler » The Life and Times of TDD) |
(Notes++) |
||
| Line 1: | Line 1: | ||
[[TDD]]: | |||
*is an approach that combines {{p|test-first development}} (TFD) and {{p|refactor code}}; | |||
*writes a test before it writes the code—the test in effect does double duty in that it both specifies and validates that piece of code; | |||
*can be used to specify detailed requirements on a just-in-time (JIT) basis throughout construction—writing the acceptance test ''is'' the documentation; a.k.a. {{p|acceptance test-driven development}} or {{p|behavior-driven development}}; | |||
*makes small changes to a product that do not change its semantics—in other words, {{p|refactor code}} is a clean-up activity that makes something better but does not add or subtract functionality; | |||
==Sources== | ==Sources== | ||
{{WebSourceListItem | {{WebSourceListItem | ||
Revision as of 08:44, 5 September 2014
TDD:
- is an approach that combines test-first development (TFD) and refactor code;
- writes a test before it writes the code—the test in effect does double duty in that it both specifies and validates that piece of code;
- can be used to specify detailed requirements on a just-in-time (JIT) basis throughout construction—writing the acceptance test is the documentation; a.k.a. acceptance test-driven development or behavior-driven development;
- makes small changes to a product that do not change its semantics—in other words, refactor code is a clean-up activity that makes something better but does not add or subtract functionality;