Swipe to navigate through the chapters of this book
In this chapter I’ll focus on three types of testing. The first two types, Unit and User Interface testing, are integrated into Xcode and are added in when you initially create your project if you’ve selected them in the appropriate dialog. These are tests managed by you, the iOS software engineer. You create Unit Tests first, knowing what is and is not acceptable behavior in your code. By setting up these behaviors as tests before you code, it’s easy to test against your requirements as you code. That’s really the point. Don’t think of these Unit Tests as something we add on to a project to check off a box somewhere; imagine them as a slightly different way to write the software project requirements. Even the most loosely based development houses manage their requirements in some manner. Using Unit Tests not only provides a convenient centralized spot to do so, but because of their tight integration with Xcode, you get requirements verification basically for free.
Please log in to get access to this content
To get access to this content you need the following product:
Molly K. Maskrey
- Sequence number
- Chapter number
- Chapter 12