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

Unit testing frameworks

We have seen xUnit, and we have briefly spoken about MSTest and NUnit. This section will give you a feeling of what these other frameworks are about.

MSTest

MSTest used to be popular, as it was installed as part of Visual Studio (VS) in the older versions of VS. Prior to NuGet’s existence, using a built-in library could cut configuration and deployment time compared to adding and using another framework such as NUnit.

Before NuGet, installing a new library involved manually copying DLLs, putting them in the right location, changing some configurations, and pushing them into source control for the team to share the same files. So, having a pre-installed library and one that didn’t require configuration, such as MSTest, was a blessing. We have moved a long way since then.

To add an MSTest project into your solution, you can do it via the UI:

Figure A1.1 – Adding MSTest via the UI

Notice that there are two...