Automated Unit Testing in Visual Studio 2005

1
Automated Unit Testing in Visual Studio 2005

• David OHara
• david_at_davidohara.net
• http//blog.davidohara.net/

2
How do you test?
3
How we test
Which would you rather use?
4
What are we talking about?

• AUT ! TDD
• If it's worth building, it's worth testing.
• - Scott Ambler

5
Why we dont test

• Not my job
• Not enough time
• Too hard

6
Unit Testing Frameworks

• NUnit
• http//nunit.com/
• MbUnit
• http//mbunit.com/
• MSUnit
• http//tinyurl.com/2nqzqj/

7
Test Runners

• TestDriven.Net
• http//testdriven.net/
• Zanebug
• http//adapdev.com/zanebug/
• Resharper
• http//jetbrains.com/resharper/

8
Am I done?
9
Project Setup
10
Bowling game Demo
11
Reality of Testability
12
Dependency Injection
13
The Problem
14
Mock Frameworks

• Nunit.Mocks
• http//nunit.org/
• Rhino.Mocks
• http//ayende.com/products/rhino-mocks.aspx
• NMock
• http//nmock.org/
• TypeMock
• http//typemock.com/

15
Purchase System Demo
16
Conclusion

• Testing is worth the effort and time
• Practice, practice, practice
• Dependency Injection separates out hard stuff
• Mocks and stubs are your friends