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

The Automation guideline

When we say automation, we mean CI. CI has a dedicated chapter in this book, Chapter 11, Implementing Continuous Integration with GitHub Actions, so we won’t go into the details here.

This guideline is about realizing that the unit tests will run on other platforms than your local development machine. So, how do you make sure your unit tests are ready for automation?

CI automation from day 1

Agile teams dedicate the first sprint to setting up the environment, including the CI pipeline. This is usually called sprint or iteration zero. If CI is set up from day 1 to listen to source control, there is less chance it is omitted or a CI-incompatible test is introduced.

Implement CI from the start of the project.

Platform-independent

.NET is multi-platform and the trend nowadays is to use Linux servers to run CI pipelines. Also, the developer dev machine can be Windows, macOS, or Linux.

Make sure your code does not rely on any OS-specific...