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

Speaker listing


Following the functionality in our C# backend, we will start by testing a listing of the speakers available. We are not yet ready to connect to the backend and, for any of the tests we will write here as unit tests, we will need to mock the behaviors that the backend would normally present.

For the moment, we are not going to concern ourselves with any kind of authentication. So, the important functionality we will be looking to implement is that when no speakers exist we should let the user know, and when speakers do exist we should list them.

The way that we will produce both situations is through a mock API. As strange as it may seem, most of our business logic will be in the mock API. Because it will be crucial to all of the other tests we will write, we must unit test the mock API as if it were production code.

A mock API service

To begin testing the mock API service, let's create a new services folder and add a mockSpeakerService.spec.js file.

Inside that file, we need to...