TestArchitect Agent is an essential component
in allowing TestArchitect to communicate with iOS devices during automated
TestArchitect Agent is installed onto an iOS device in
a two-step process involving re-signing of the Agent, followed by its installation.
Ensure that basic requirements are met before installing TestArchitect Agent
onto an iOS device (see the section Prerequisites
following procedures for re-signing the TestArchitect Agent app can only be performed from an
If the test machine does not yet have a development private key already imported into
the Keychain Access application, go ahead and import the private key file (*.p12) on your
If you need to export the development private key from another test machine, select Keychain Access window, click
login in the Keychains panel, then
click Keys in the Category panel. In the
Name panel, expand the imported private key node you want to
use, right-click the certificate, select Export and save the
. In the
Import a development private key file (*.p12) into the test machine's Keychain
Access by double-clicking the private key file. If requested, enter the file's
The development private key is imported into Keychain Access on the test
Obtain the full name of the private key of your iOS developer account from
Open Keychain Access from
In the Keychain Access window, click
login in the Keychains panel, and then
click Keys in the Category panel.
In the Name panel, expand the imported private key node you
want to use, right-click the certificate, and select Get Info
on the context menu.
Make note of the device's provisional Common Name.
Place the following files into a folder with full read and write permissions.
- The provisional profile file (*.mobileprovision)
TestArchitectAgent.ipa, FileInfo and
iOSInstrumentationDyLib.dylib files can be found at the following
location when TestArchitect is installed:
Start the command line terminal and navigate to the directory to which you copied the
files in the preceding step.
Make the script file resign.sh executable by entering the
following command to the terminal, followed by pressing
chmod +x resign.sh
Execute the resign.sh script with the name of
the private key obtained in the earlier step as the first parameter, the name of the
provisional profile file as the second parameter, and the name of the application file to
re-sign as the third parameter.
key in Keychain Access> <file name
of the provisional profile>
(without or with the .ipa
suffix) of the application file to re-sign>
Note: Providing the file name's extension
(.ipa) is optional. If not provided, the script assumes an
extension of .ipa.
./resign.sh "iPhone Developer: John Doe (3M2DBQ46ZG)"
The resign.sh script terminates
with the message replacing existing signature, to indicate
that re-signing was successful.
Connect the iOS device to the test machine using a USB cable, and install a re-signed
TestArchitect Agent onto the device with iTunes.
Double-click the TestArchitectAgent.ipa file that you
Using iTunes, synchronize TestArchitect Agent with the
A re-signed TestArchitect Agent is installed onto the
may be performed on either an macOS or Windows machine.
You must synchronize essential TestArchitect Agent development
libraries with the iOS device before TestArchitect Agent can be
launched on the device.
If you haven't done so already, connect the iOS device to the test machine using a
Start Xcode on the test machine and wait at least ten seconds before disconnecting
the iOS device or closing Xcode.
Important: TestArchitect Agent
libraries are purged each
time the iOS device restarts or reboots. Therefore, in order to run the Agent on a
rebooted iOS device, you must resynchronize the TestArchitect Agent
development libraries with the device by repeating step 8
After installing a re-signed TestArchitect Agent onto an iOS device, the TestArchitect Agent icon is visible on the device's desktop.