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

Abstracting the data layer


The data layer abstraction has already begun with the implementation of a repository pattern. In this section, we will work to create a valid abstraction for connecting to an Entity Framework. After we can communicate with the Entity Framework, we will then focus on making the repository more generic and able to work with multiple data models.

Extending the repository pattern

The first step in creating a valid data layer abstraction is to make sure CRUD has been handled. CRUD (Create, Read, Update, and Delete) are the basic operations that can be performed on any dataset. The IRepository does not yet provide access to all of these capabilities so we will begin by extending it.

First create a folder to contain the tests for a SpeakerRepository. The folder should be named in line with the folders containing the SpeakerService tests and SpeakerController tests. As usual, we start with a failing test. In this case, the test is failing to compile:

[Trait("Category", "SpeakerRepository...