You can watch this episode by subscribing to Cocoacasts Plus.

Building a Weather Application From Scratch

Exposing Gaps in the Test Suite

by Bart Jacobs | Dec 25, 2018 | Swift
Last Updated on Dec 25, 2018

Swift 4 Xcode 10 iOS 12

Building a Weather Application From Scratch

1	Introduction 03:30
2	Setting Up the Project Plus 07:15
3	View Controller Containment Plus 12:08
4	Fetching Weather Data 05:59
5	Removing Object Literals Plus 07:54
6	Creating a View Model Plus 13:09
7	Parsing the JSON Response Plus 13:56
8	Handling Errors and Notifying the User Plus 14:28
9	Adding Flexibility With Protocols Plus 14:11
10	Creating the Day and Week View Models Plus 07:33
11	Creating the User Interface of the Day View Controller Plus 12:52
12	Organizing Fonts and Colors Plus 06:45
13	Implementing the Day View Model 15:55
14	Writing Unit Tests for the Day View Model Plus 12:57
15	Implementing the Week View Model Plus 12:37
16	Writing Unit Tests for the Week View Model Plus 07:10
17	Fetching Weather Data for the User's Location Plus 13:32
18	Increasing Testability With Protocol-Oriented Programming 14:47
19	Replacing Optionals with Enums and Associated Values Plus 09:30
20	Efficiently Refreshing Weather Data Plus 08:48
21	Adding Pull to Refresh Plus 09:40
22	Unit Testing With Mock Objects Plus 10:49
23	Unit Testing Asynchronous Code Plus 06:40
24	Mocking Network Requests Plus 08:28
25	Exposing Gaps in the Test Suite Plus 04:00
26	Filling In the Gaps of the Test Suite Plus 13:16
27	Mocking Network Requests With Mockingjay 07:48

Stop Writing Swift That Sucks

DISCLAIMER: No Rocket Science Involved

Join 20,000+ Developers Learning About Swift Development

Download the 4 Swift Patterns I Swear By

The interface of the RootViewModel class shows that we only need to unit test the initializer and the refresh() method. I explained earlier why I don't unit test the initializer and, in the previous episodes, we unit tested the refresh() method. Does that mean that the test suite now completely covers the RootViewModel class? The answer is no. This is a common mistake developers make. In this episode, we collect code coverage data to expose the gaps in the test suite.

Instant and Unlimited Access
to 400+ Cocoacasts Tutorials

Monthly

$19 / month

Pay Once a Month
Access to Community
30 Day Money Back Guarantee

Get Started

Yearly

$8.25 / month (billed annually)

Pay Once a Year and Save $129
Access to Community
30 Day Money Back Guarantee
Access to All Books

Get Started

Building a Weather Application From Scratch

Exposing Gaps in the Test Suite

Instant and Unlimited Accessto 400+ Cocoacasts Tutorials

Instant and Unlimited Access
to 400+ Cocoacasts Tutorials