To test mobile apps, you must import them or upload them
to IBM® Rational® Test Workbench. 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.
Before you begin
To upload apps from a mobile device, the mobile device
must be running the mobile test client and
be connected to test workbench.
For more information on configuring the mobile device, see Configuring
the mobile client if you are testing native or hybrid applications
using the mobile test client on
Android/devices or iOS simulators.
The Android SDK must be installed
on the workbench computer. You must install the Android SDK mentioned
in the section of
http://developer.android.com/sdk/index.html.
Note: This
web site is not maintained by IBM and the location of SDK might change
in the future.
The app must be installed on the mobile
device.
About this task
When you upload your application from a device or simulator
and it is being instrumented, depending on the size of the application,
this might take a few seconds to several minutes. If you are testing
complex applications, in some cases, you might receive an out-of-memory
error. The solution could be to increase the memory allocation on
the computer where
IBM Rational Test Workbench is installed. For more details, see
Increasing
memory allocation to upload applicationsProcedure
To upload an app from a mobile device:
- In the mobile test client,
tap Upload app.
- Select an installed app from the list and tap Upload. The Mobile and Web UI applications editor
opens in Rational Test
Workbench and
displays the app with a Processing tag until
the app is fully uploaded and instrumented for testing. When an original
package is created and copied in your workspace, it means that the
application is instrumented. The Test Navigator displays
the application in Incoming applications.
- Incoming applications must be managed to be used in a test,
in other words, the instrumented version of the application must be
added to a project in the test workbench. To manage the
AUT, right-click the incoming application and select Generate
managed application. In the wizard that opens up, select
or create a project or folder to save the .ma resource that contains
your original mobile application package. You can change the .ma file
name.
- Click Finish. The application is
displayed in the Mobile and Web UI application editor
and in the Test Navigator under Mobile
and Web UI applications. The application is ready for
all the test stages and it is identified as a managed application
on the mobile device.
What to do next
When the application is ready, you can record your test.
For more information, see
Recording tests from the Android mobile test client