A small

1. Test Driven Development
By Joshua Candish

2. Unit Testing & TDD
What is it?

3. How TDD works
We have a problem to solve…
Let’s think about writing some code to solve it!

4. STOP

5. How TDD works
Instead, write a unit test for the problem.
Fails…
Then write the code to make the test pass.

6. The Three Laws
You may not write production code unless you’ve first written a failing unit test.
You may not write more of a unit test than is sufficient to fail.
You may not write more production code than is sufficient to make the failing
unit test pass.

7. Why?
Modifying code/refactoring
Produces robust code
Ability to release code at any time
Code Coverage

8. Why Not?
Time factor
Difficult in large projects
Learning Curve
Might not suit the company

9. Continuous Deployment

10. Testing Frameworks
Nunit
Mspec
Microsoft Test Tools (Visual Studio)
Junit, Runit, Xunit etc….

11. Test Runners
Ncrunch (bloody expensive) - continuous
MightyMoose (open source) – continuous
ReSharper

12. References
Dogsa, T., & Batic, D. (2011). The effectiveness of test-driven development: An industrial case study. Software
Quality Journal, 19(4), 643-661.
Sangwan, R. S., & LaPlante LaPlante, P.,A. (2006). Test-driven development in large projects. IT Professional
Magazine, 8(5), 25-29.
Vodde, B., & Koskela, L. (2007). Learning test-driven development by counting lines. IEEE Software, 24(3), 74.
Hunt, A., & Thomas, B. (2009). Pragmatic unit testing: In c# with nunit. The Pragmatic Programmers.
Martin, R. C. (2007). Professionalism and test-driven development. IEEE Software, 24(3), 32.
Janzen, D., & Saiedian, H. (2008). Does test-driven development really improve software design quality? IEEE
Software, 25(2), 77-84.
Crispin, L. (2006). Driving software quality: How test-driven development impacts software quality. IEEE Software,
23(6), 70-71.

13. Demo Time 