This section includes several tasks that are specific to managing Android
applications.
Uploading Android applications from the mobile test client
To test mobile apps, you must import them or upload them
to Rational® Test Workbench Mobile
Test Edition. When you upload the application in the test workbench from a mobile device,
the application is instrumented and recompiled into two new apps:
a recording-ready application and a playback-ready application. The
recording version contains the application under test, augmented with
code and the playback version is the original version with a test
workbench certificate. An original package must be uploaded for each
application to test and saved in the workbench. They allow you to
either record a test or run a test. Then the application must be saved
in a test workbench project
to be ready for test.
Adding Android apps to the test workbench from the command line
You can automate the process of adding Android apps to the test workbench with the AddAndroidApp.jar command
line tool, which you can download from the Android Welcome Page. This tool instruments the
application under test and then adds it to the test workbench.
Instrumenting Android applications in a shell-sharing environment
If you are working in an environment in which Rational Test Workbench Mobile
Test Edition & Android Development Toolkit (ADT)
are shell-shared, you can automatically import Android applications
in the test workbench,
launch the instrumentation of the applications, and make them ready
for recording and running tests.
Testing pre-installed applications on Android devices
Before you can test certain Android applications, you must rebuild them by providing a
private key. Examples of such applications are those that are pre-installed on devices or APIs that
need administrator or root-level permissions.