Content Comparison

• Windows/Linux/Mac:

gspt init --greenspectorApi "https://core-saas-prod.greenspector.com/api" --privateToken [MYTOKEN]

gspt ping

gspt initprojectconfiguration --application [APP-NAME] --version [VERSION]

Please replace [APP-NAME] and [VERSION] with the information used in the previous section.

gspt testbench set-environment

Available environments: 
1 - mobile: Samsung - Galaxy S7 with android 8 
2 - mobile: pixelc with android 8.1.0 
3 - mobile: Samsung - Galaxy S9 with android 10 
4 - mobile: Samsung - Galaxy S9 - with sim with android 10 
5 - mobile: Samsung - Galaxy S9 - Maintenance with android 10 
6 - mobile: Samsung - Galaxy S22 with android 13 
7 - mobile: Samsung - Galaxy Tab S7 FE with android 13 
8 - mobile: Samsung - Galaxy S10 with android 12 
9 - mobile: Samsung - Galaxy S10 - with sim with android 12 
Please choose an environment:

gspt testbench custom-tests --testsSuite launch:./script.testgb --monitoredPackage "com.android.chrome" --iterations=3 -e config-skipsetupphone=false --networkMode=Wifi -e PAUSEDURATION=30000 -e PAUSEAFTERLOAD=1000

--app [package name of app] # ex : --app com.google.android.youtube

-app [path to the apk] # ex : --app ./my_apk.apk

--app [path to the apk] # ex : --app https://my-website.com/my-apk.apk

gspt testbench custom-tests --testsSuite launch:./script.testgb --monitoredPackage [appPackageName] --iterations=3 -e config-skipsetupphone=false --networkMode=Wifi -e PAUSEDURATION=30000 -e PAUSEAFTERLOAD=1000 --app [appPackageName]

Mandatory option*

• --apkFileapp: APK (s) to measure. The apk file could be a local path, a public URL or a package name to download from the PlayStore. Prefer separate APKs for your app and for your tests.

• --testsSuite* : Gdsl script name and lists of test files writen with Greenspector DSL. All test files will be launched in the specified order.

• --monitoredPackage* : Name of the android package. Probes can monitor multi package at a time. In this case, metrics are agreggated. For website, choose com.android.chrome.

• --iterations: Number of iterations of measure wanted. (Default: 1).

• --report: Automatically generate the test report in the .greenspector folder and wait for the job to end.(Default: false). 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.

• --extra: Use to transmit extras parameters with the format name=value. (exemple --e PARAMETERNAME="value" will replace all ${PARAMETERNAME} in the GDSL file by value).

• --networkMode: The network mode for the test. Values can be "WIFI", "4G", "3G" or "2G". (Default: WIFI).

• --disable-dumpsys: Disable Android System Monitoring. By default, this is enabled and will add one iteration to your job for more detailed metrics (Views, Activity, OpenSSL Sockets, ...). If no need these metrics, disable this iteration, it will reduce testing time.

• --only-dumpsys: Run only a Android System Monitoring iteration. This iteration will only be able to retrieve Android System metrics (Views, Activity, OpenSSL Sockets, ...).

Please verify theses parameters to have relevant measurements:

• PAUSEDURATION: 30000

• PAUSEAFTERLOAD: 1000

• config-skipsetupphone: false

• iterations: 3

Note that extras in job.yml which contains text, as PSWD for example, can’t contain a “!” because it’s interpreted by the bash. To know more about it go to the Troubleshooting tool.

If the test doesn’t succeed, refer to Measure Troubleshooting

If the test succeeds, congratulations!

Check the consistency of measures with Verification of measures consistency

• First, click on Benchmark in the side menu:

• Choose + Add an application, enter name and validate. Description field is optional.

• Choose + Add a version, and give a version name:

• Choose a test environment. The list shows the available devices on our testbench :

• Specify the type of the item to measure: Website or Mobile app

• For website, enter the URL for a website

• For application, enter:

  • A link to the .apk file

  • A package name which will be downloaded on Google Playstore

• Enter the amount of times the benchmark has to be executed:

  • The higher the number, the better the precision, but also the longer the execution time.

• For a website, specify the browser to use

Follow the measurement process

The Tests tracking tab allows to verify if the test is taking into account by the testbench:

• When Pending, the test is waiting for an available device in testbench

• When Running, the test is currently running on a device

• When Finished, the results are available

Waiting time depends of the availability of testbench devices.

At the end, click on the test to get more information, as logs, screenshots or dump. They stay available for 7 days.

• Go in Analysis portfolio

• Click on New Analysis

• Select Benchmark

• Enter needed information

• Validate

Verify that all rules have been evaluated : 24 rules should be verified.

If it is not the case, re launch benchmark.

This feature allows you to run a measure of a website on the TestBench.
To use this feature, you have to first configure the application name, version and the environment to run the measure on.
The command to run is:

gspt testbench measure-url --url [URL]

Options

Mandatory option*

• --url* : URL to benchmark

• --iterations: Number of iterations of measure (Default: 1).

• --browser: Browser to run the measure on. (Default: Google Chrome).

• --networkMode: Network mode for the test. Values can be "WIFI", "4G", "3G" or "2G". (Default: WIFI).

• --report: Automatically generate the test report in the .greenspector folder and wait for the job to end. (Default: false).

This command will send a measure request to the server. After this measure has run on the Power Test Bench/Cloud, results are available on the web interface.

Examples

gspt testbench measure-url --url https://greenspector.com/ 
gspt testbench measure-url --url https://greenspector.com/ --iterations 5 --browser chrome --networkMode 4G 
gspt testbench measure-url --url https://www.mozilla.org/fr/ --browser firefox --report

This feature allows to benchmark an Android application on the TestBench.
To use this feature, you have to first configure the application name, version and the environment to run the measure on.
The command to run is:

gspt testbench benchmark-apk --app [APK-PATH]

Options

Mandatory option*

• --app* : APK(s) to benchmark. (If set multiple times, all the APK will be installed but only the first one will be launched and monitored). Can be a local path, a public URL or a package name to download from the PlayStore. Optional if the applications to benchmark are already installed on phone

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

• --report: Automatically generate the test report in the .greenspector folder and wait for the job to end. (Default: false).

• --networkMode: The network mode for the test. Values can be "WIFI", "4G", "3G" or "2G". (Default: WIFI).

This command will send a measure request to the server. After this measure has run on the Test Bench, you will find the results on the Web Interface.

Example

gspt testbench benchmark-apk --app target/final.apk # local path to apkgspt testbench benchmark-apk --app https://demo/demo.apk # apk from public urlgspt testbench benchmark-apk --app com.microsoft.office.outlook # package name to download the apk from the PlayStoregspt testbench benchmark-apk --app target/main.apk --app target/app-module.apk --app target/commons.apk --networkMode 3G # three apk to install and launch benchmark in 3Ggspt testbench benchmark-apk --app target/final.apk --iterations 5 --report # Launch 5 iterations of the benchmark and wait for the report