Book Image

Hands-On Design Patterns with Swift

By : Florent Vilmart, Giordano Scalzo, Sergio De Simone
Book Image

Hands-On Design Patterns with Swift

By: Florent Vilmart, Giordano Scalzo, Sergio De Simone

Overview of this book

Swift keeps gaining traction not only amongst Apple developers but also as a server-side language. This book demonstrates how to apply design patterns and best practices in real-life situations, whether that's for new or already existing projects. You’ll begin with a quick refresher on Swift, the compiler, the standard library, and the foundation, followed by the Cocoa design patterns – the ones at the core of many cocoa libraries – to follow up with the creational, structural, and behavioral patterns as defined by the GoF. You'll get acquainted with application architecture, as well as the most popular architectural design patterns, such as MVC and MVVM, and learn to use them in the context of Swift. In addition, you’ll walk through dependency injection and functional reactive programming. Special emphasis will be given to techniques to handle concurrency, including callbacks, futures and promises, and reactive programming. These techniques will help you adopt a test-driven approach to your workflow in order to use Swift Package Manager and integrate the framework into the original code base, along with Unit and UI testing. By the end of the book, you'll be able to build applications that are scalable, faster, and easier to maintain.
Table of Contents (22 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Advanced testing with mocks, spy, and others


As we have seen, testing part of the software when it doesn't depend on other parts of the same app is quite straightforward:

  1. Create an instance of the class
  2. Set an initial context
  3. Trigger some behavior to change the state or to return a new set of values

This is even easier if the class being tested is well-designed and has only a single well-defined responsibility. However, it's not common to have a class that depends on other classes, or, even more complicated, a class that depends on external collaborators, such as databases, a network service, or user input.

In the next section, we'll see a technique to test this scenario. The nomenclature we use is the one defined by Gerard Meszaros in his seminal bookXunit test Patterns,Chapter 11,Using Test Doubles, and now widely used in the industry.

Testing in Isolation

When the class we want to test depends on other classes, we have two choices: test all the classes it depends on, or try to isolate it and...