You're reading from Pragmatic Test-Driven Development in C# and .NET Write loosely coupled, documented, and high-quality code with DDD using familiar tools and libraries

Product type Paperback

Published in Sep 2022

Publisher Packt

ISBN-13 9781803230191

Length 372 pages

Edition 1st Edition

Languages

Tools

.NET

Concepts

Test Driven Development

Author (1):

Adam Tibi

View More author details

Table of Contents (21) Chapters

Preface

1. Part 1: Getting Started and the Basics of TDD

2. Chapter 1: Writing Your First TDD Implementation FREE CHAPTER

3. Chapter 2: Understanding Dependency Injection by Example

4. Chapter 3: Getting Started with Unit Testing

5. Chapter 4: Real Unit Testing with Test Doubles

6. Chapter 5: Test-Driven Development Explained

7. Chapter 6: The FIRSTHAND Guidelines of TDD

8. Part 2: Building an Application with TDD

9. Chapter 7: A Pragmatic View of Domain-Driven Design

10. Chapter 8: Designing an Appointment Booking App

11. Chapter 9: Building an Appointment Booking App with Entity Framework and Relational DB

12. Chapter 10: Building an App with Repositories and Document DB

13. Part 3: Applying TDD to Your Projects

14. Chapter 11: Implementing Continuous Integration with GitHub Actions

15. Chapter 12: Dealing with Brownfield Projects

16. Chapter 13: The Intricacies of Rolling Out TDD

17. Index

Why subscribe?

18. Other Books You May Enjoy

Appendix 1: Commonly Used Libraries with Unit Tests

1. Appendix 2: Advanced Mocking Scenarios

Introduction to continuous integration

The idea behind the term CI is that new code is continuously integrated with existing code, which results in a system that can be shipped to production at any time (or at least this is the intention).

The route from software development to production is referred to as the release pipeline, where the code passes through multiple processes to reach production, such as compiling the code, deploying the binaries on the dev environment, allowing a QA to pull the code to a certain environment, and others. CI is an integral part of the release pipeline.

A CI system requires a host so that it can do various operations on the code. The host is a combination of a server and an operating system:

Figure 11.1 – CI server in an OS

Here are a few examples of on-premise CI servers: