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

Issues that prevent adding tests 


Deadlines are tight. The scope is ever changing. We just don't have time to write tests. It's more important to get functionality out the door. We've all been there. Whatever the case may be, sometimes you will find yourself working on a project that was not written with testing in mind.

Note

There never seems to be enough time to do it right, but there's always time to do it over.

So, what are the issues you might face that would prevent you from adding tests to a legacy application?

When a system wasn't written with testing in mind, it can be quite difficult to go back and add tests at a later date. Classes with concrete dependencies and tight coupling make software applications difficult to test. Things such as large classes and functions, Law of Demeter violations, global state, and static methods can also make for a system that can be very difficult to test.

Much like building a house by starting with a shaky foundation, untestable code begets untestable...