Rebuilding an Android application with a private key

A default certificate is used to build Android applications when they are managed in the test workbench. However, some applications must be signed with a private key before you can create a test. This is the case in applications that use web mapping services. If such applications are built with the default certificate, the maps might not show up properly in the tests. You can assign a private key to an Android application and rebuild the application in the Mobile and Web UI Applications editor.

Before you begin

You must import the application under test to the test workbench. You can use the Add application wizard from the Mobile and Web UI Applications editor: see Importing applications to test in the workbench. Alternatively, you can upload the application by using the Upload application option from the IBM® Rational® Test Workbench Mobile Client, Upload application: see Uploading Android applications from the mobile client.

About this task

This task applies to Android applications only.

Procedure

  1. In the Mobile and Web UI Applications editor, right-click an application and click Rebuild Application. If you want to build the application with a new version of the application, you must import a new version in the editor first.
  2. Select Sign application with your own private key in the dialog box and click yes to rebuild the application.
  3. In the wizard that opens, browse to select a keystore file, enter a Keystore password, then select an Alias and enter the Alias password, click OK. When the build process is completed, the application under test is signed and the private key (the certificate) for that alias is embedded in the .apk file. Thus, the application is rebuilt, re-instrumented and made ready for recording and testing.

Feedback