Testing has always interested me to some degree. Not from the perspective of manual testing or quality assurance, but from the perspective of the developer behind the desk who just wrote the code. How can a developer, who is accountable for their own code, ensure that they are producing the highest quality code with a low defect count and high maintainability rating? One answer for many years now has been the development process of TDD, or Test Driven Development.
TDD is not just about unit tests; it’s actually an entire thought process with a set of core fundamentals you should follow, and it really changes the way you think about your code, and eventually the way you write it.
I did a thirty minute screencast on TDD in an introductory manner. I go through the steps of designing and building a simplified inversion of control container through the process of TDD.
Video
Watch on YouTube now.
Source Code download:
Download from my Skydrive
Powerpoint Slides
Download from my Skydrive
Related Posts
ViewModel constructors and inheritance by extending kendo.data.ObservableObject
Exploring Active Record as a base for business entities in a business logic layer with Entity Framework- Using your own database schema and classes with ASP.NET Core Identity and Entity Framework Core
- Using DataTestMethod and DataRow to pass parameters to a unit test and prevent duplicating test methods
- Building SSDT SSRS projects (.rptproj) with a build server (TeamCity)
- Threads, locks, deadlocks, race conditions, and thread safety in multi-threaded code