160 likes | 286 Views
Automated Unit Testing in Visual Studio 2005. David O’Hara david@davidohara.net http://blog.davidohara.net/. How do you test?. How we test. Which would you rather use?. What are we talking about?. AUT != TDD “If it's worth building, it's worth testing.” - Scott Ambler.
E N D
Automated Unit Testing in Visual Studio 2005 David O’Hara david@davidohara.net http://blog.davidohara.net/
How we test Which would you rather use?
What are we talking about? AUT != TDD “If it's worth building, it's worth testing.” - Scott Ambler
Why we don’t test • Not my job • Not enough time • Too hard
Unit Testing Frameworks • NUnit • http://nunit.com/ • MbUnit • http://mbunit.com/ • MSUnit • http://tinyurl.com/2nqzqj/
Test Runners • TestDriven.Net • http://testdriven.net/ • Zanebug • http://adapdev.com/zanebug/ • Resharper • http://jetbrains.com/resharper/
Mock Frameworks • Nunit.Mocks • http://nunit.org/ • Rhino.Mocks • http://ayende.com/products/rhino-mocks.aspx • NMock • http://nmock.org/ • TypeMock • http://typemock.com/
Conclusion • Testing is worth the effort and time • Practice, practice, practice • Dependency Injection separates out hard stuff • Mocks and stubs are your friends