Skip to main content

Manually Instrumenting iOS Applications

info

Please note that this tool is classified as a Legacy tool. We recommend transitioning to our updated solutions to maintain optimal performance and security in your workflows. For more information on this matter, please reach out to technical support .

info

Use this process only if you cannot use the iOS Application Instrumentation because you don't have an iOS certificate or provisioning profile.

We provide three instrumented iOS demo applications (the links, below, can be opened only from iOS devices):

  • EriBank can also be found under installation folder: <install dir>\bin\ipas(activity name: com.experitest.ExperiBank)

  • QuickContactsTest (activity name: com.experitest.QuickContacts)

  • UICatalogTest (activity name: com.experitest.UICatalogTest)

We also provide an instrumented browser application, SimpleBrowser, for web testing using the Web identification method (activity name: com.experitest.browser)

This preparation needs to be performed only once for the application.

  1. Open your project in Xcode.

  2. Duplicate the target.

  3. If asked about the new Duplicate Target choose "Duplicate Only".
     

  4. If desired, double-click the name of the duplicated target, then rename it.

  5. Click the duplicated target.

  6. Click Build Phases -> Link Binary With Libraries.

  7. Add the required the libraries your project.

    1. Enter the name of the library into the search bar, then click Add.

    2. Repeat for each library needed.

      info

      These libraries that must be added to the project:

      • CFNetwork.framework
      • QuartzCore.framework
      • UIKit.framework
      • Foundation.framework
      • CoreGraphics.framework If you use the Simulate Capture Feature, these must also be added.:
      • CoreFoundation.framework
      • AVFoundation.framework
      • CoreMedia.framework
      • CoreVideo.framework
      • CoreImage.framework
      • Vision.framework If you use the Mock Authentication feature, these must also be added:
      • LocalAuthentication.framework
      • Security.framework
      info

      To make sure a library was indeed added to the Link Binary With Libraries list, check the list for the framework that you just added.

  8. Click Add Other.

  9. Add Experitest.framework. It should be in the installation folder, under /bin/native. If it isn't, download it here.
    **

    **

  10. Click Open.

  11. If you use the Simulate Capture Feature, add CameraControl.framework.

  12. If you use the Mock Authentication Feature, add MockAuth.framework. 

info
  • Open the .zip file only on a Mac machine. Opening it using Windows and then copying it to a Mac machine will result in problems with instrumentation.
  • After unzipping the file, attach the <*.framework> located within the folder, and not the folder itself.
info

If the linker fails to find Experitest.framework, locate the framework file and drag it manually into Xcode's project navigator. If the issue persists, locate the "Framework Search Paths" option in "Build Settings" and manually add the Experitest.framework directory.

  1. Click Build Phase -> Link Binary With Libraries.
info
  • When updating the Experitest framework, make sure the framework is not removed from the linked libraries.
  • Make sure all the  required libraries have been added to the project.
  1. Click Build Settings , then search for "other linker flag".
  2. Add following linker flags:
  • -all_load
  • -ObjC
  1. Click Build Settings -> Other Linker Flags.
info

When updating the Experitest framework, make sure the linker flags do not change for the duplicated build settings.

**

**

  1. Click Product -> Scheme -> New Scheme.

  2. Add the new target (the duplicated target made in the steps prior to this one).

  3. Click the duplicated target and deploy the application onto the device.
    **

**

  1. Switch between the targets to run with and without the Continuous Testing Cloud server.

  2. In order for the application to advertise itself as instrumented in cloud UI, add the following structure to the applications's Info.plist:

Info.plist

<key>ExperiInstrumentationInfo</key>
<dict>
	<key>InstrumentationCapabilities</key>
    <dict>
		<key>MockCamera</key>
		<true/> <!-- or false if the CameraControl.framework was not added -->
		<key>MockAuthentication</key>
		<true/> <!-- or false if the MockAuth.framework was not added -->
	</dict>
</dict>
  1. Make sure the instrumentation is working correctly by launching it in the cloud and verifying the different capabilities (object spy, image upload, etc.)
Last updated on