Book Image

Test-Driven iOS Development with Swift - Fourth Edition

By : Dr. Dominik Hauser
Book Image

Test-Driven iOS Development with Swift - Fourth Edition

By: Dr. Dominik Hauser

Overview of this book

Test-driven development (TDD) is a proven way to find software bugs earlier on in software development. Writing tests before you code improves the structure and maintainability of your apps, and so using TDD in combination with Swift 5.5's improved syntax leaves you with no excuse for writing bad code. Developers working with iOS will be able to put their knowledge to work with this practical guide to TDD in iOS. This book will help you grasp the fundamentals and show you how to run TDD with Xcode. You'll learn how to test network code, navigate between different parts of the app, run asynchronous tests, and much more. Using practical, real-world examples, you'll begin with an overview of the TDD workflow and get to grips with unit testing concepts and code cycles. You'll then develop an entire iOS app using TDD while exploring different strategies for writing tests for models, view controllers, and networking code. Additionally, you'll explore how to test the user interface and business logic of iOS apps and even write tests for the network layer of the sample app. By the end of this TDD book, you'll be able to implement TDD methodologies comfortably in your day-to-day development for building scalable and robust applications.
Table of Contents (17 chapters)
Section 1 –The Basics of Test-Driven iOS Development
Section 2 –The Data Model
Section 3 –Views and View Controllers
Section 4 –Networking and Navigation

Setting up and tearing down

We have already seen the setUpWithError() and tearDownWithError() instance methods earlier in this chapter. The code in the setUpWithError() instance method is run before each test invocation. In our example, we used setUpWithError() to initialize the Blogger that we wanted to test. As it was run before each test invocation, each test used its own instance of Blogger. The changes we made to this particular instance in one test didn't affect the other test. The tests are executed independently of each other.

The tearDownWithError() instance method is run after each test invocation. Use tearDownWithError() to perform the necessary cleanup. In the example, we set the blogger to nil in the tearDownWithError() method.

In addition to the instance methods, there are also the setUp() and tearDown() class methods. These are run before and after all the tests of a test case, respectively.