CSC/ECE 517 Fall 2012/ch2a 2w31 up: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 32: | Line 32: | ||
== See Also == | == See Also == | ||
*[http://www.slideshare.net/Skud/test-driven-development-tutorial TDD in different languagues] | *[http://www.slideshare.net/Skud/test-driven-development-tutorial TDD in different languagues] | ||
*[http://www.agiledata.org/essays/tdd.html Disciplined Agile Delivery (DAD): A Practitioner’s Guide to Agile Software Delivery in the Enterprise by Scott W. Ambler and Mark Lines, IBM Press, ISBN: 0132810131] | |||
=== Books === | |||
* [http://www.amazon.com/Test-Driven-Development-By-Example/dp/0321146530 Test Driven Development: By Example , Kent Beck] | |||
* [http://www.agiledata.org/essays/tdd.html Disciplined Agile Delivery (DAD): A Practitioner’s Guide to Agile Software Delivery in the Enterprise by Scott W. Ambler and Mark Lines, IBM Press, ISBN: 0132810131] | |||
Revision as of 19:39, 19 October 2012
SaaS - 5.3 - The TDD cycle: red-green-refactor
Introduction
Test Driven Development is an evolutionary approach to software development that requires a developer to write test code before that actual code and then write the minimum code to pass that test. This process is done iteratively to ensure that all units in the application are tested for optimum functionality, both individually and in synergy with others. This produces applications of high quality in less time.
TDD vs BDD
Advantages and Disadvantages
Advantages
ensures the code is tested and enables you to retest your code quickly and easily, since it’s automated.
Seams
Red – Green – Refactor
• Capture that thought in a test, which fails! • Write the simplest possible code that lets the test pass! • Refactor: DRY out commonality w/other tests! • Continue with next thing code should do !
Examples
References
<references/>