Unit Testing and Test-Driven Development (TDD) arguably mean the same thing. They (both describe a way of developing software so that you always know whether or not it's working. You write little chunks of code (unit tests) that verify the objects and methods in your application's code and it helps you make sure that you have PROOF that your code works. It also makes your code easier to maintain and easier to refactor. Plus, while it might not feel like it right away, writing using tests makes your development process go a lot faster.
In this session, Ben will discuss what unit testing & TDD are all about, why you should care, and how to do it with C# and ASP.NET MVC. Along the way, expect to hear about "designing for testability" and some really helpful testability design patterns like the Strategy, Repository, and Adapter patterns.
You will learn:
- Why write unit tests
- How to write unit tests
- How to think about technical debt and code written without unit test and making it testable