Scheduling Information for Mobile Application Targets¶
When you schedule a test for a mobile application, several conditions should be considered.
The steps you take to schedule an application for a depend on these three factors:
- Whether the service is 3D (unlimited) or limited
- Whether the test is standard (Mobile-S) or comprehensive (Mobile-C)
- Whether the application runs on one mobile operating system only (Android or iOS), or whether it runs on both systems
If the service is unlimited, then follow the steps described in the "Scheduling Information for Mobile Applications" section.
If the service is limited, follow the instructions in this table:
| Scope of test | One system or both systems? | How to schedule |
|---|---|---|
| Mobile-S | 1 system | Do not specify remote endpoints. |
| Mobile-S | Both systems | Create a target for each OS. Assign both targets to the same service. Do not specify remote endpoints. |
| Mobile-C | 1 system | Specify remote endpoints. |
| Mobile-C | Both systems | Create a target for each OS. Assign both targets to the same service. Specify remote endpoints for the first target but (usually) not the second. See the note that follows. |
Note: Not specifying endpoints for the second target makes that test a Mobile-S test rather than a Mobile-C test. Usually this makes sense: The first, comprehensive target has tested the server-side behavior already. However, if server-side behavior differs in the iOS app compared to the Android app, then specify remote endpoints for both targets. Both tests will be comprehensive, and between them will check the behavior of both the iOS app and the Android app.
Parent topic:Scheduling Tests for Mobile Application Targets
Related information