...

 gspt testbench custom-tests --apkFiles <path to APK> --testPackages <Test package to launch> --monitoredPackagemonitoredPackages <package to monitor>

Examples:

...

2 - --testPackages: For each APK containing functional tests you want to launch (i.e. UI Automator or Espresso APK tests), precise the name of the android package (i.e. package in file AndroidManifest.xml). All tests in those Android packages will be launched. Mandatory option: Minimum 1

3 - --monitoredPackage: The package name of the monitoredPackages: For each Android application to monitor with the probes you want to monitored, precise the name of the android package to get metrics about the process (process data, process CPU…). Probes can monitor only one multi package at a time. In this case, metrics are agreggated. For website, choose the browser where the tests runs (i.e. com.android.chrome). Mandatory option: Exactly  Minimum 1

4 - --iterations: Number of iterations of measure you want. (Default: 1). Optional

...

This command will send a measure request to the server. After this measure will ran on the Power Test Bench/Cloud, you will find the results on the Web Interface.

Some options are deprecated:

1 - --monitoredPackage: The package name of the Android application to monitor with the probes to get metrics about the process (process data, process CPU…). Probes can monitor only one package at a time. For website, choose the browser where the tests runs (i.e. com.android.chrome). Mandatory option: Exactly 1 (This option is deprecated, use monitoredPackages)

Related articles