Prerequisites
Resource plans for basic testing are purchased, or resource usage does not exceed the free quota. For more information, see Pricing.
The Android app that you want to test is uploaded. For more information, see Upload an app.
A use case set for functional testing is created or imported. For more information, see Create or import a use case set.
A script is uploaded or recorded online, and a use case is created. For more information, see Create a use case.
The Mobile Testing console page is displayed. For more information, see Go to the Mobile Testing console page.
Procedure
Step 1: In the left-side navigation pane of the Mobile Testing console, choose Testing Products > Functional Testing.
Step 2: Select the Android app that you want to test from the app drop-down list.
The Android app that you want to test must be uploaded in advance. If it is not uploaded, click Upload App to upload it. For more information, see Upload an app.
Step 3: Click Submit Test to go to the Run Functional Testing page.

Step 4: On the Run Functional Testing page, configure the test. For more information, see Configuration description.
Step 5: After the test is configured, move the pointer over Submit Test. The number of estimated required cycles in resource plans is displayed.

If the value specified by Estimated Required Cycles in Resource Plans exceeds the free quota of the account or the total quota of purchased resource plans, click Buy Resource Plan to purchase resource plans for basic testing .
Step 6: Click Submit Test.

After the test is submitted, the test waits to be executed in the queue. After the test is executed, you can view the complete test report.
Configuration description
Select App and Version

Parameter | Description |
---|---|
App Package | The app that is uploaded or selected by default. The app package can be changed. |
App Version | The version of the app that is uploaded or selected by default. If multiple app versions exist, select the version that can be used for functional testing. |
Test Remarks | The information of the test, which facilitates subsequent query and review. |
Test Configurations

The following table describes the parameters contained in the Basic Information section.
Parameter | Description |
---|---|
Official Edition/Trial Edition |
For more information, see Pricing. |
Select Model | Step 1: Click Select Model. In the Select Test Model panel, select a model from the model list or select one or more preset options to batch select models. ![]() Step 2: Select one or more preset options to batch select brands and models and add them to the Selected list. Step 3: Enter a brand and a model in the search box to filter brands and models. Fuzzy match is supported. Step 4: Select one or more devices to add them to the Selected list. Step 5: In the Selected list, perform the following operations:
Step 6: Click OK to save the model list. |

The following table describes the parameters contained in the Test Configurations section.
Parameter | Description |
---|---|
Use Case Library Version | The use case library version of the use case set that is used for functional testing. |
Test Use Case Set | The use case set that is used for functional testing. Note Use case sets must be configured in advance. If no use case sets are configured, you can click Use Cases. On the Scripts tab of the page that appears, you can configure a use case set. For more information, see Create or import a use case set. |
Parameter Group | The parameter group related to a use case set that is used for functional testing. Note Parameter groups related to use case sets for logon must be configured in advance. For more information, see Create a parameter group. |
Account Conflict | Specifies whether the account can be used to log on to the app only from a single device. |
Email Address | The email address that is used to receive notifications after functional testing is complete. |