Book Overview & Buying
Table Of Contents

C# and .NET Core Test-Driven Development

By : Ayobami Adewole

3 (7)

Buy this Book

C# and .NET Core Test-Driven Development

3 (7)

By: Ayobami Adewole

Buy this Book

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.

Preface

Who this book is for

What this book covers

To get the most out of this book

Get in touch

Free Chapter

Exploring Test-Driven Development

Difficulty in maintaining code

How does bad code appear?

What we can do to prevent bad code

The principles of test-driven development

The TDD cycle

Summary

Getting Started with .NET Core

.NET Core framework

Structure of a .NET Core application

Tour of Microsoft's Visual Studio Code editor

A look at the new features of C# 7

Creating an ASP.NET MVC Core application

Summary

Writing Testable Code

Warning signs when writing untestable code

Law of Demeter

The SOLID architecture principles

Setting up a DI container for ASP.NET Core MVC

Summary

.NET Core Unit Testing

The attributes of a good unit test

Unit testing framework ecosystem for .NET Core and C#

Unit testing consideration for ASP.NET MVC Core

Structuring unit tests with xUnit

xUnit.net shared test context

Live unit testing with Visual Studio 2017 Enterprise

Proving unit test results with xUnit.net assertions

The test runners available on both .NET Core and Windows

Summary

Data-Driven Unit Tests

The benefits of data-driven unit testing

xUnit.net theory attribute for creating data-driven tests

Inline data-driven unit tests

Property data-driven unit tests

Integrating data from other sources

Summary

Mocking Dependencies

The benefits of mocking objects

The shortcomings of mocking frameworks

Hand-rolling mocks versus using a mocking framework

Mocking objects using Moq framework

Summary

Continuous Integration and Project Hosting

Continuous integration

Continuous delivery

GitHub online project hosting

Basic Git commands

Configuring GitHub WebHooks

TeamCity CI platform

Summary

Creating Continuous Integration Build Processes

Installing the Cake Bootstrapper

Writing build scripts in C#

Cake Extension for Visual Studio

Using Cake tasks to build steps

CI with Visual Studio Team Services

Summary

Testing and Packaging the Application

Executing xUnit.net tests with Cake

.NET Core versioning

.NET Core packages and metapackages

Packaging for NuGet distribution

Summary

Other Books You May Enjoy

Leave a review - let other readers know what you think

Continuous integration

Continuous integration (CI) is a software development practice where the source code of software projects is integrated by members of a software development team daily into a repository. It is preferably started at an early stage of the development process. The code integration is usually carried out by a CI tool that performs the verification of the code using an automated build script.

In a development team, there are often multiple developers working on different portions of a project, with the source code of the project hosted in a repository. Each developer can have a local version or working copy of the main branch or mainline on their computer.

A developer working on a feature will make a change to the local copy, and test the code using a set of prepared automated tests to ensure that the code works and does not break any existing working functionalities...

Tech Concepts

Programming languages

Tech Tools