Book Image

Test-Driven iOS Development with Swift 4 - Third Edition

By : Dr. Dominik Hauser
Book Image

Test-Driven iOS Development with Swift 4 - Third Edition

By: Dr. Dominik Hauser

Overview of this book

Test-driven development (TDD) is a proven way to find software bugs early. Writing tests before you code improves the structure and maintainability of your apps. Using TDD, in combination with Swift 4's improved syntax, means there is no longer any excuse for writing bad code. This book will help you understand the process of TDD and how to apply it to your apps written in Swift. Through practical, real-world examples, you’ll learn how to implement TDD in context. You will begin with an overview of the TDD workflow and then delve into unit-testing concepts and code cycles. You will also plan and structure your test-driven iOS app, and write tests to drive the development of view controllers and helper classes. Next, you’ll learn how to write tests for network code and explore how the test-driven approach—in combination with stubs—helps you write network code even before the backend component is finished. Finally, the book will guide you through the next steps to becoming a testing expert by discussing integration tests, Behavior Driven Development (BDD), open source testing frameworks, and UI Tests (introduced in Xcode 9).
Table of Contents (9 chapters)

Testing Network Code

Most apps in the App Store perform networking in one way or the other. Apple provides a great class for network requests--URLSession. Its requests are asynchronous. This means that the response is delivered on a background thread. If that wasn't the case, the UI would freeze while the app waits for a response from the server.

The main topic of this chapter is how to test an asynchronous API. There are two ways to write tests for asynchronous API calls. First, it can be done using the real server that is going to be used when the app is in the App Store. Second, it can be done using stubs, as we did in the previous chapter.

Both methods have their advantages. Tests with the real server let us additionally test whether the server is implemented as described in the documentation. Those tests are closer to the implementation of the finished app and, therefore...