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

Reviewing the requirements


In order to get started, the foundation of the speaker section of the Speaker Meet application is laid by defining the initial set of requirements. These will help eliminate ambiguity and develop a common understanding of the requirements, as well as defining a common vocabulary used throughout the project.

The abstract is where a projects, purpose and value can be presented. Any project, before it can be approved to be worked on, must prove the value that it can provide to the company. This is true whether you are working for a Fortune 500 company or a startup with two people.

A data dictionary is important because it provides a common, ubiquitous language for the project. The term, ubiquitous language, is from Domain Driven Design and denotes a shared or common language. The idea is that the shared jargon of the business and development team is solidified in a codex that can be viewed and used by all.

Last, and certainly not least, the requirements must be presented...