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

Testing direction


Now that you have a basic plan for your architecture you have to think about where you should begin your testing. There are a few options for where to start:

  • You could choose to start testing at the data access or data source layers and work your way up to the user interface layers. This method is a back-to-front approach to testing.
  • You could start at the user interface layers and work your way to the data access layers. Approaching the tests in this manner is a front-to-back method of testing.
  • Lastly, you could start testing in the business layers and work your way out to the hexagonal boundaries of the system. This method is an inside-out testing approach.

As a demonstration of the three testing directions to be examined, the same scenario of user login will be used.

Back-to-front

Most back-end developers have been taught to think in a database-first manner. This style of thinking will lead them to find that a back-to-front style of testing makes more sense. As mentioned previously...