Retired Document
Important: This version of Unit Testing Guide has been retired. The replacement document focuses on the new testing features and workflow provided by Xcode 5 and later revisions. For information covering the same subject area as this page, please see Testing with Xcode.
Glossary
- application unit tests
Unit tests that test the operation of code in a running app. These tests can ensure that an app’s data model, user-interface elements, and controllers are connected correctly and interact as expected. However, application unit tests are not user-interface tests. Application unit tests do not directly manipulate user-interface elements, and the running app does not initiate a run loop.
- logic unit test
Unit tests that test the operation of code in isolation. These tests ensure that units of code (a single procedure or a set of related procedures) behave as expected.
- run destination
The simulator, device, or architecture on which Xcode runs a product runs after builds it:
iOS: The run destination can be a simulator or an iOS device.
Mac: The run destination is your Mac device, in the 64-bit or 32-bit architectures.
- test case
A set of criteria that determines whether one or more procedures function correctly. See test case method.
- test case method
An Objective-C method that calls one or more procedures to test the correct operation of the unit. When the unit behaves incorrectly, the test case fails. When a test case fails, it calls a test result macro to report the failure.
- test suite
A
SenTestCase
subclass. A test suite contains one or more test cases. See test case.
Copyright © 2013 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2013-09-18