Book Image

C# and .NET Core Test Driven Development

By : Ayobami Adewole
Book Image

C# and .NET Core Test Driven Development

By: Ayobami Adewole

Overview of this book

This book guides developers to create robust, production-ready C# 7 and .NET Core applications through the practice of test-driven development process. In C# and .NET Core Test-Driven Development, you will learn the different stages of the TDD life cycle, basics of TDD, best practices, and anti-patterns. It will teach you how to create an ASP.NET Core MVC sample application, write testable code with SOLID principles and set up a dependency injection for your sample application. Next, you will learn the xUnit testing framework and learn how to use its attributes and assertions. You’ll see how to create data-driven unit tests and mock dependencies in your code. You will understand the difference between running and debugging your tests on .NET Core on LINUX versus Windows and Visual Studio. As you move forward, you will be able to create a healthy continuous integration process for your sample application using GitHub, TeamCity, Cake, and Microsoft VSTS. By the end of this book, you will have learned how to write clean and robust code through the effective practice of TDD, set up CI build steps to test and build applications as well as how to package application for deployment on NuGet.
Table of Contents (11 chapters)

Hand-rolling mocks versus using a mocking framework

Using a mocking framework can facilitate a smooth unit testing experience, especially when unit testing a portion of code with dependencies in which mock objects are created and substituted for the dependencies. While it is easier using mocking frameworks, you might sometimes prefer to hand-roll mock objects for your unit tests and not add extra complexity or additional libraries to your project or code base.

Hand-rolled mocks are classes that are created for the purpose of testing and used to replace production objects. These created classes will have equivalent methods as the production classes with the same definitions and return values to effectively simulate the production classes and to use as substitute for dependencies in unit tests.

...