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

An N-Tiered hexagonal architecture


In a previous chapter, the N-Tiered architecture was discussed, where a software application is divided up into layers. N-Tiered applications are typically separated in successive layers, like the layers of a cake, from A to B to C and so on. There is a danger in defining an application in this way, as sometimes pieces of functionality don't cleanly fall into one layer. As long as the layers remain loosely coupled and functionality does not cross the boundaries, your application should remain well-structured and organized.

Hexagonal architecture

The hexagonal architecture was first described by Alistair Cockburn in the 2000s. Hexagonal architecture has also been referred to as ports and adapters, in which ports are abstractions and adapters are the implementations. This approach to designing applications changes the concept of layers to one of internal and external pieces to the application.

Some may argue that the hexagonal architecture and N-Tiered architecture...