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

Digesting the problem


The problem the application will be designed to solve has been defined. Speaker Meet will bring technology speakers, communities, and conferences together. Now that the purpose has been defined, it must be digested.

As was suggested before in a previous chapter, attacking a new application from all directions is ill-advised. It can be quite a daunting task to attempt to approach a new software project by implementing each and every desired feature all at once. It can also be a large chore to define every want and need of the system.

It would be far better to define small, manageable chunks of the application that can be delivered quickly in order to evaluate their correctness and effectiveness. The trouble is, how does one define what can be separated into small pieces and determine that this small piece is of sufficient value?

Epics, features, and stories; oh my!

Many software development projects will maintain what is referred to as a product backlog. This is where everything...