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

TODO app  


The TODO app was another one of our early TDD examples. This app is far from complete, and we have received new requirements from the business, asking to add a feature to the application.

The business now wants the ability to complete a task in the TODO list. This feature is schedule current sprint and is the next story for us to work on.

Mark complete

For the Mark complete story, we have been asked to allow the user to complete any of the tasks in the TODO list. Adding this feature should be much like any other TDD exercise in this book. Before reading our solution to this problem, try to complete this one on your own. After you have passing tests, come back and look at the solution in this book.

Adding tests

In the ToDoApplicationTests file, we have added a yak shaving test to force us to create the complete method. This test also helps to define the API for the method:

[Fact(Skip = "Yak shaving - no longer needed")]
public void CompleteTodoExists()
{
  // Arrange
  var todo = new...