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 objects using Moq framework

Selecting a mock framework to use for mocking objects is important for a smooth unit testing experience. However, there are no written rules to be followed for this. You can consider some factors and features of the mocking framework when selecting a mocking framework for use in your tests.

Performance and available features should be the first factors to be considered when selecting a mocking framework. You should examine the way the mocking framework creates mocks; frameworks that use inheritance, virtual, and static methods cannot be mocked. Other features to look out for can be methods, properties, events, and even if the framework supports LINQ.

Additionally, nothing beats simplicity and the ease of use of a library. You should go for a framework that is easy to use, with good documentation of the available features. In the subsequent sections...