Book Image

Practical Test-Driven Development using C# 7

By : John Callaway, Clayton Hunt
Book Image

Practical Test-Driven Development using C# 7

By: John Callaway, Clayton Hunt

Overview of this book

Test-Driven Development (TDD) is a methodology that helps you to write as little as code as possible to satisfy software requirements, and ensures that what you've written does what it's supposed to do. If you're looking for a practical resource on Test-Driven Development this is the book for you. You've found a practical end-to-end guide that will help you implement Test-Driven Techniques for your software development projects. You will learn from industry standard patterns and practices, and shift from a conventional approach to a modern and efficient software testing approach in C# and JavaScript. This book starts with the basics of TDD and the components of a simple unit test. Then we look at setting up the testing framework so that you can easily run your tests in your development environment. You will then see the importance of defining and testing boundaries, abstracting away third-party code (including the .NET Framework), and working with different types of test double such as spies, mocks, and fakes. Moving on, you will learn how to think like a TDD developer when it comes to application development. Next, you'll focus on writing tests for new/changing requirements and covering newly discovered bugs, along with how to test JavaScript applications and perform integration testing. You’ll also learn how to identify code that is inherently un-testable, and identify some of the major problems with legacy applications that weren’t written with testability in mind. By the end of the book, you’ll have all the TDD skills you'll need and you’ll be able to re-enter the world as a TDD expert!
Table of Contents (21 chapters)
Title Page
Packt Upsell
Foreword
Contributors
Preface
4
What to Know Before Getting Started
Index

Configuring the API project


With the React project now configured to hit the real API, it's time to turn our attention to the .NET solution. In order to verify that everything is wired up correctly, you'll want to write a series of integration tests to ensure that the whole system is working properly.

Integration test project

Create a new xUnit Project called SpeakerMeet.Api.IntegrationTest within the existing solution. This will be where the .NET integration tests will be created. You may want to explore separating these out according to your preferences and/or team coding standards, but that can wait. For now, a single integration test project will do.

For our purposes, we'll be testing whether the system functions from API entry all the way to the database, and back. However, it's best to start small test individual integration points, and grow from there.

Where to begin?

You could certainly start by creating a test that will call an API endpoint. In order to achieve this, an HTTP Request...