To help you meet the demands of mobile users, Test Studio offers automated responsive testing enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
As of March 1, 2020, native mobile testing is no longer supported.
The application configured following the steps below, should be used for testing purposes only and will not be accepted in Apple App Store.
- Open your project in Xcode. This guide uses the open source application Wikipedia as an example.
Select the project file in Xcode in order to view the list of Targets.
Right click the target for testing and click Duplicate.
Rename the new target to
This signifies that the target is a QA-only build, and should not be used as a release.
Since Xcode does not do it automatically, update the new target’s associated files, settings, and schemes to reflect the new target name.
Update the build settings to properly reference any property list files you rename.
This table contains the items to update when a target is duplicated:
Target ApplicationName copy > ApplicationNameQA Target .plist file ApplicationName copy-Info.plist > ApplicationNameQA.plist Target > Build Settings > Packaging > Info.plist File ApplicationName copy-Info.plist > ApplicationNameQA.plist Target > Build Settings > Packaging > Product Name ApplicationName copy > ApplicationNameQA Scheme > Manage Schemes ApplicationName copy > ApplicationNameQA
If you're using the Wikipedia app as an example and intend to deploy it to your device, modify the following setting to build it with your own credentials: Target > Summary > iOS Application Target > Bundle Identifier.
- Select the new target in the Scheme drop-down.
- Download the Test Studio Mobile extension for iOS and unpack it.
/MobileTestingExtension_iOS/and drag libMobileTestingExtension.a into your Project's file listing.
If you target to automate WKWebView's in your project, drag libMobileTestingWebKit.a into your Project's file listing as well.
Select Create folder references for any added folders.
- Uncheck the original target and check the new QA target.
Go to Build Phases > Link Binary With Libraries. A reference to the testing extension is automatically added. Add libicucore.tbd, Security.framework, QuartzCore.framework and CFNetwork.framework if they are not already linked. In older versions of Xcode you may need to add libicucore.dylib instead of libicucore.tbd. This grants WebSocket compatibiltiy.
If you target to automate WKWebView's in your project, WebKit.framework must also be added.
Go to Build Settings > Linking and add
-add_loadto Other Linker Flags.
This ensures all symbols from the static libraries compile correctly into the target application.
Go to the Info tab of the
QAtarget's settings and click + to add a new URL Type.
- Identifier: com.telerik.automation
- URL Schemes: APPLICATIONNAME
- Role: Editor
The URL Schemes should not contain any spaces. The APPLICATIONNAME portion need not match your duplicate Target name exactly, however we recommend consistency. The only requirement is that APPLICATIONNAME is unique so it does not conflict with another testable application.
If you deploy the app to an iOS 9+ device then you must use one of the names listed below:
Select the newly configured target and click Run.
Build Succeededmessage, you may have to wait up to 10 seconds for the application to deploy. The device's screen will be black in the meantime.
You may need to close your application (and the app) on the device before deploying.
The Application Identifier is setup during the instrumentation process of the testable app. The Application Identifier is combination of URL Schemes suffixed with ://.
When used in Test Studio Mobile, the
Application Identifiermust be suffixed with ://. For example, the app identifier that is setup in previous section is WikipediamobileQA (no trailing colon and slashes), but suffixed with :// when entered in the Test Studio Mobile Set Application ID dialog.
iOS 9 introduces a feature that requires user confirmation when Mobile Testing Agent app starts an app under test. As a result a confirmation dialog is shown the first time tests are run and after the first test is executed. Once Open is chosen for both dialogs they won't be presented any more. However the first execution may still fail because of the interruption caused by the dialogs.