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

Moving forward


So, where do you go from here? Hopefully, you're as excited about TDD as you were when you first successfully compiled a software application. Each successive passing test is proof of your hard work and understanding of the problem at hand. Celebrate each small victory for the accomplishment that it is. Validate your understanding along the way by introducing more and more functionality to the system through your tests.

As you continue in your career, it is up to you to choose to operate in a TDD fashion. Adherence to the philosophy and how well you maintain the TDD mindset is completely up to you. Don't be discouraged if your boss isn’t familiar with TDD. You don't need permission.

Continue to grow applications through tests. If others ask about TDD, share your knowledge and enthusiasm. Introduce the practice to your team, but do not force the practice on anyone who is not ready.

TDD is a personal practice

First and foremost, TDD is a personal practice. It should not be a line...