Share this page
Automatic signing services
To enable users to sign apps when uploading them to OpenText Functional Testing Lab, the administrator needs to set up the signing services.
About app signing services
Whenever an app is repackaged with OpenText Functional Testing Lab record and replay libraries, the app needs to be re-signed. By default, Android apps are signed with a debug certificate, and no additional action is required by the administrator. For iOS apps, or for Android apps that use services requiring a private key such as Google Maps or the Authentication service, the administrator needs to set up for automatic signing.
You can also package and sign apps manually and then upload them to OpenText Functional Testing Lab. For details, see Package an Android app manually or Package an iOS app manually with the packager service.
Signing service for iOS apps
You set up the iOS signing service so that iOS apps can be signed when they are uploaded to OpenText Functional Testing Lab. The signing service is also used for signing the Agents. For details, see iOS signing service.
OpenText Core SDP and OpenText Core Functional Testing Lab:
Configure the embedded signing service. When this service is set up, the Agents and all other apps uploaded to OpenText Functional Testing Lab can be signed with your Apple certificate and provisioning profile. Alternatively, if you choose not to set up automatic signing, you can manually sign the Agents and your apps using the iOS Enabler. For details, see Package an iOS app manually with the iOS Enabler.
Signing service for Android apps requiring a private key
This section is not relevant for OpenText Core SDP and OpenText Core Functional Testing Lab.
In general, packaging of Android apps on upload to OpenText Functional Testing Lab requires no additional action. To view the settings configured for the Android packager, click Administration 
> Settings tab and select Android packaging service. For more details, see Administration settings.
By default, your apps are signed with a debug certificate. If your app uses services that require a private key, for example Google Maps or the Authentication service, you need to sign your app with your own private key during the packaging process. To enable OpenText Functional Testing Lab to sign using a private key, you need configure the app packager to use your signing details.
To configure automatic signing with your app with your own certificate:
- Open the packager properties file on the OpenText Functional Testing Lab Server machine:
Operating system Details Linux: <Path to your server installation folder>/server/conf/packager.propertiesWindows: <Path to your server installation folder>\server\conf\packager.properties - Enter the following information:
- ANDROID_KEYSTORE_PATH = The path to your key store, which is a binary file containing your set of private keys.
- ANDROID_KEY_PASSWORD = The password for the private key to be used to sign the app.
- ANDROID_STORE_PASSWORD = The password for the key store.
- ANDROID_ALIAS_NAME =The name used to identify the private key entry in the key store.
Note: All four values are required. If any of the values is left empty, the app packaging process fails.
OpenText Core SDP and OpenText Core Functional Testing Lab:
By default, apps are signed with a debug certificate. If your app uses services that require a private key, for example Google Maps or the Authentication service, you can package the app manually and then upload it. For details, see Package an Android app manually.
Troubleshooting the app packager
There may be times when the packaging process does not succeed. When a packaged version of the app cannot be created, a notification is displayed. For details on troubleshooting the app packager, see App Packager.
Packaging is not essential for testing, however, there are certain test cases that require the app to be packaged. For details, see When to use a packaged app.
See also:
