Book Image

Pragmatic Test-Driven Development in C# and .NET

By : Adam Tibi
Book Image

Pragmatic Test-Driven Development in C# and .NET

By: Adam Tibi

Overview of this book

Test-driven development is a manifesto for incrementally adding features to a product but starting with the unit tests first. Today’s project templates come with unit tests by default and implementing them has become an expectation. It’s no surprise that TDD/unit tests feature in most job specifications and are important ingredients for most interviews and coding challenges. Adopting TDD will enforce good design practices and expedite your journey toward becoming a better coding architect. This book goes beyond the theoretical debates and focuses on familiarizing you with TDD in a real-world setting by using popular frameworks such as ASP.NET Core and Entity Framework. The book starts with the foundational elements before showing you how to use Visual Studio 2022 to build an appointment booking web application. To mimic real-life, you’ll be using EF, SQL Server, and Cosmos, and utilize patterns including repository, service, and builder. This book will also familiarize you with domain-driven design (DDD) and other software best practices, including SOLID and FIRSTHAND. By the end of this TDD book, you’ll have become confident enough to champion a TDD implementation. You’ll also be equipped with a business and technical case for rolling out TDD or unit testing to present to your management and colleagues.
Table of Contents (21 chapters)
1
Part 1: Getting Started and the Basics of TDD
8
Part 2: Building an Application with TDD
13
Part 3: Applying TDD to Your Projects

Implementing Continuous Integration with GitHub Actions

You wrote unit tests and other types of tests and you are happy about your code coverage and quality. So far so good, but who is going to make sure these tests are going to run every time the code changes? Is it the developer that is pushing new code? What if they forget? What if there are merge problems in source control that might break your tests? Who is going to check?

You’ve already figured out the answer. It is the continuous integration (CI) system that you should have in place. CI is the natural companion to unit testing, and you can rarely find a modern project today without a CI system in place.

In this chapter, we will cover the following:

  • An introduction to continuous integration
  • Implementing a CI process with GitHub Actions

By the end of the chapter, you will be able to implement an end-to-end CI process with GitHub Actions.