This talk was give at the South Shore .NET Users Group. Unit Testing is now considered a required skill for developers. There are a ton of tools out there. However, there's nothing that shows you how to tie them all together to make your software fast, testable, and flexible. This talk will go over my toolset: • MSTest • Moq - Mocking framework • NCover - for coverage • MSBuild - for automation • Dotcover - coverage from VS • Unity - for dependency injection This talk has a very long demo

1. Unit Testing and Tools
@wbsimms
@southshorenet

2. Vocabulary
Unit test
•
Code you write to test your code
Coverage
•
Measure of how much code is tested
Mock
•
Replacement for something else
Dependency Injection (DI)
•
•
Builder design pattern
Object and dependencies are created for you
Continuous Integration (CI)
• Responds to checkins, builds code, and generates code
metrics (coverage, unit test pass fail, etc.)

3. Why Unit Test?
Which would you rather do?
Write Tests
Fix
Production
Bugs

4. That’s cute… but really… why?
1) Catches regression bugs at the
developers desk
2) Documents how code works
3) Catalog of the business rules

5. What makes a good unit test?
•
•
•
•
Repeatable
Fast
Test by layers
Good Coverage

6. Layers?
Web
• Controllers
• ViewModels
• Helpers
DataAccessLayer
• Repositories (or what ever)
• Models
• Helpers
Other Libraries
• Rules Logic
• Etc…

7. Test documentation?
1. public void MethodName_Case_ExpectedResultTest()
2. [Description(“Your text here”)]
public void MethodNameCaseTest()

8. When to run your test?
All tests all the
time!





After pull / sync
Before commits
During CI builds
Before you merge
After you merge

9. So… the tools?
• MSTest
•
Unit testing framework
• Moq
•
Creating mock objects from interfaces
• Unity
•
Dependency Injection
• MSBuild
•
Build automation
• DotCover/Ncover
•
For coverage analysis

10. Demo time…
Deep breath….