If you want to prove that a complex system works, a good place to start is to check that each piece is working right. Unit testing intends to do just that: take a unit of your code, and verify that it behaves properly. Unfortunately, in “real” software, classes interact with other parts of the system, which makes testing in isolation difficult. Mocking is a technique designed to overcome that issue: replacing dependencies by Mocks, lightweight versions of the “real thing”, allows you to validate the interactions of a class with its “collaborators”.
I will discuss reasons you should care about mocks, illustrate how you would go about addressing them by rolling your own mocks & stubs, and demonstrate free, open-source frameworks, Moq, Rhino.Mocks and NSubstitute, which greatly simplify the process. Mocks and Stubs can sound intimidating – the goal of this presentation is to demystify the topic and give you a clear understanding of what they are, where they can help you, and to give you a good quick-start so that you can productively use them in your own code.
Mathias Brandewinder has been writing software in C# for 7 years, and loving every minute of it, except maybe for a few release days. He enjoys arguing about code and how to make it better, and gets very excited when discussing TDD or F#. His other professional interests are applied math and probability. If you want to know more about him, you can check out his blog here (http://www.siliconvalley-codecamp.com/www.clear-lines.com/blog) or his rants on Twitter as @brandewinder (https://twitter.com/#!/brandewinder).
6:00 doors open (pizza and drinks) 6:10 - 6:25 Lightning talks 6:30 announcements 6:45 - 8:15 presentation 8:15 - 8:30 raffle Sponsors
Can't code without (http://www.jetbrains.com/resharper/features/index.html?linklogos)