In this episode Matthew and Federico sit with fellow team member Brad Wilson to talk about Unit Testing. Brad is a developer in the ASP.NET team, he has a lot of experience developing using Test Driven Development and is one of the creators of the xUnit testing framework.

  • What is Unit Testing?
  • What is the difference between Unit Testing and Test Driven Development (TDD)?
  • Unit Testing in practice
    • How does the MVC team uses unit testing?
    • How do you arrange your tests?
    • How do you name your tests?
    • What about using internal to be able to test something?
    • What if I inherited code that didn't had unit tests?
    • How can I convince my team to adopt unit tests as a development practice
  • Addressing common concerns about Unit Testing
    • It feels like a lot of work for little value.
    • Having to rewrite a lot of tests if something in the design changes is a pain.
    • Code ends up being a lot of very small methods and I don’t like that.
  • Common pitfalls
    • Writing very big tests.
    • Testing to internal implementation.
  • Mocking
    • What does mocking mean and why is it useful?
    • What is your favorite mocking framework?
  • Resources


Listen now (Flash required):