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

Introducing TDD to your team


At this point, you are probably quite excited at sharing the wonderful world of TDD with your organization and fellow team members. Be aware that others may not have the same enthusiasm. Writing unit tests may be a scary proposition to someone that has never tried it before. There may be some negative connotations associated with the idea for some on your team.

As developers, we're paid to be the experts. We're expected to have the answers. When something new and unknown is introduced, it can be an anxiety-inducing experience. Work towards reducing the anxiety your team might feel when learning something new. Remember how it felt when you heard the term TDD and didn’t know where to begin. Think about how you felt before picking up this book.

There are good ways and not so good ways to introduce TDD to your team. If you truly want your team to adopt the practice, then think about ways in which to get them excited about the prospect.

Don’t force TDD on anyone

There...