To share tests with your team members and work in a collaborative
environment, you must retain the resource file (.ma file) that is
generated when an application under test is added to the test workbench.
A possible scenario could be that a developer working with a project
team collaboration tool (for example, Rational Team Concert) delivers
an application so that it can be tested by a teammate who is a software
test specialist.
The .ma resource file is created when you upload an application
from the
mobile test client or
when you import an application in the
test workbench. It is created
in the following two ways for all native Android, iOS, hybrid, and
web applications.
- When you upload an application from an Android mobile test client, or from the rtwBuildXcode.sh
script, for iOS applications, a message indicates in the Mobile
and Web Ui applications editor of the test workbench that an incoming
application must be managed to be used in a test (see figure 1). To
manage the application, click the button on the right of the dialog
box (see figure 1).
Figure 1: Manage the incoming application
In the wizard that opens, you must indicate a project and folder
to save the managed application (see figure 2).
Figure 2: Enter, create or select a project to save the .ma
file
When you click
Finish, the .ma file is
built and saved in the
test workbench (see
figure 3):
Figure 3: The .ma file is generated
When the application is added or uploaded to the
test workbench, it is automatically
instrumented first, that is to say, augmented with code, and then,
it is managed (the file is saved in the test workbench to be ready
for testing).
- When you add an application to the test workbench from the Mobile
and Web UI applications editor, you must indicate where to get the
application, and where to save the application that will be generated.
When you click Finish, the application is instrumented
and a .ma file is built.
The different uses of the .ma file: - You can send an exported test or set of tests with the .ma file
to a teammate, by using Test Assets with Dependencies or Test Assets
with Dependencies in the context menu of the Test
navigator view. You can import tests from archive files
so that you will be in the same resources to run the tests: the .ma
will be automatically used to add this AUT to the list of applications
on the test workbench.
Figure 4: Export test assets with dependencies including the
.ma file
Figure 5: Import test assets with dependencies including the
.ma file
- A .ma file is useful if you use a collaboration tool to share
and manage source code with teammates. You can deliver the .ma file
and your teammates can import it so the application appears in their
applications list. When you work with a collaboration tool and import
a test resource file, if the application is not listed in the Mobile
and Web UI applications editor, you are prompted to import
the application in the workspace (see figure 6). To do so, double
click the .ma file in the Test Navigator. You
are asked if you want to import the application. Click Yes (see
figure 7). The application is shown in the list of applications available
in the test workbench.
Figure 6: To add the application to the list, double-click the
.ma file in the Test Navigator.
Figure 7: Dialog that shows up when you double-click the .ma
file in the Test Navigator.
Note: The .ma file contains everything that is needed to test
the application. For Android, it contains the original apk files,
so your teammates can run the tests on any device or emulator that
is connected to their test workbench.