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)

Mocking Dependencies

In Chapter 5, Data-Driven Unit Tests, we discussed data-driven unit testing using the xUnit framework, which allows us to create tests that run on data from different sources, such as flat files, databases, or inline data. Now, we will explain the concepts of mocking dependencies and explore how to use the Moq framework to isolate your class that is being tested from its dependencies, using mock objects created with Moq.

There are usually objects dependencies in the code base of software projects, whether for a simple or a complex project. This is because the various objects need to interact and share information across boundaries. However, to effectively unit test the objects and isolate their behaviors, each object must be tested in isolation, irrespective of the dependencies it has on other objects.

In order to achieve this, the dependent objects in a class...