Test Driven Development Facts and Fallacies
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Test Driven DevelopmentFacts and Fallacies
Overview of Fallacies
#1 - Not enough time
#2 - Just for Unit tests?
#3 – Fad
#4 – Not for real work
Quality
Stress
Manual
Testing
Gerry Weinberg
Quality Software Management, 1991
Stress
Automated
Testing
Defects
260
100
Project Non-TDD Project TDD
Project Non-TDD
Project TDD
TDD vs. Non-TDD
Test First
Stress
1) Write
complete set
of unit tests
2) Then write
production
code.
M. M. Müller and O. Hagner, “Experiment about Test-first
Programming”, Proceedings of Conference on Empirical
Assessment in Software Engineering (EASE), 2002.
6 years published
10 Years in practice
3,650 Days in practice
Microsoft
Bosch
Sun
ObjectMentor
IBM
ThoughtWorks
Technology
Confusion
Confidence
Examples
Product Data Gateway
Compare Logical Model
Microsoft Renewals
JavaScript WebVersioning
Debugged: FileManager
Review of Fallacies
#1 - Not enough time
#2 - Just for Unit tests?
#3 – Fad
#4 – Not for real work
Thank You
Related Documents
