Next up
Build the App to be Tested
Continuing in
Testing in Xcode
This is a preview of subscription content
Your browser needs to be JavaScript capable to view this video
Try reloading this page, or reviewing your browser settings
You're watching a preview of subscription content. Log in to check access
Learn automatic testing in Xcode. Start by creating a simple test app that intentionally crashes in given scenarios. Then review the code to find obvious bad practices and issues. Discover why unit testing is important and perform a simple unit test. Work with test cases before adding functionality. Then increase code coverage and learn why it’s important. Finally work with different parts of the app to test specific functionality.
What You’ll Learn
-
Set up different UI tests for testing different parts of an app
-
Perform simple unit test cases in a project
-
Use test cases before adding functionality to ensure quality apps
Who This Video Is For
Professional developers or experienced programmers who want to incorporate best practices for testing their apps before publishing them.
About The Author
Bill Mårtensson is the owner of Magic Technology AB. He has extensive experience developing for mobile platforms, including the iPhone with Swift. He has also worked in backend development with Python, Django, and Xamarin. He has taught app development for the last seven years to over 400 students ranging from new programers to experienced developers.
About this video
- Author(s)
- Bill Mårtensson
- DOI
- https://doi.org/10.1007/978-1-4842-5192-8
- Online ISBN
- 978-1-4842-5192-8
- Total duration
- 1 hr 23 min
- Publisher
- Apress
- Copyright information
- © Bill Mårtensson 2019
Video Transcript
In these videos, we’re going to learn about automating testing in Xcode. We’re going to learn how to make sure that our app does what it should and not just believe that it works as it should. We’re going to begin by making a bad app just to introduce some errors. And then in the next part, we’re going to learn about how to automatically test different scenarios and find bugs.
To test this, I made a very simple app with a single view, which is a registration form with an email password. And the user has to enter which year they were born as a kind of age simplified age check. And they have to approve the terms and click Register. The related code for this is just I made some outlets for the different parts, the different components, and an action for the approved terms change, and the click on the button.