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

Where to begin


The best place to begin is at the beginning. Before a developer can start coding, they must know what the goal of the program is. What is the purpose of the application? Without a clear understanding of the problem that they are attempting to solve, it can be difficult to get started. At the very least, it is ill-advised to begin without some kind of plan.

The sooner you start to code, the longer the program will take.

– Roy Carlson, University of Wisconsin

Have you ever started a craft project without any objective in mind? How did you know what it was you were making? Did the project turn out well? If it did, you more than likely picked a direction at some point and set out to achieve a goal. You may have even had to start over or make adjustments along the way in order to complete the project.

Now, imagine starting the same craft project with the desired result defined ahead of time. Perhaps you wanted to make a drawing. Maybe you developed a set of plans.It isn't until a clear...