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

TDD arguments and misconceptions

Here are a few hints and tips – from my own experience – that will occur again and again in a conversation with the business or your colleagues.

Unit testing, not TDD

When discussing with the business, to reduce the complexity of the conversation, especially if the business is not tech-savvy, use the term unit testing rather than TDD. TDD is a technical process that individuals will do themselves and it is not directly related to the business, so why complicate the discussion by adding it? Sometimes the business has heard the term TDD, and they are excited about it, so then TDD is the right term to use!

My advice is to use unit testing in your conversation unless the business has some preference for the term TDD.

Unit testing is not implemented by testers

The term testing in unit testing is misleading to the non-techies as it implies a tester doing manual testing. I have had this conversation with many business individuals...