Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
For web measurements, the monitoredPackage option needs to be modified with the name of the application package.
You also need to add the app option as follows:
If the application is available on Play Store (Android) or on Apple Store (iOS):
--app [android package name of app] # ex: --app com.google.android.youtube
--app [url of the app on Apple Store] # ex: --app https://apps.apple.com/fr/app/youtube/id544007664
If the application is present with a local apk (Android) or a local ipa (iOS):
--app [path to the apk] # ex : --app ./my_app.apk
--app [path to the ipa] # ex : --app ./my_app.ipa
If the application is present with a public apk (Android) or a public ipa (iOS):
--app [path to the apk] # ex : --app https://my-website.com/my-app.apk
--app [path to the ipa] # ex : --app https://my-website.com/my-app.ipa
Use the command line below to start a measurement:
--app: apk or ipa to measure. The file could be a local path, a public URL, a package name to download from the PlayStore or an url of the app to download from the Apple Store.
--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.
Results
Results are available on :
The work folder with greenspector/dd-mm-yyyy XXhXXm/tests-results/results.txt
Benchmark is the fastest way to get result with an automated test execution. However, it does not give a personalized analysis with a precise user journey.
All the benchmark procedure takes place on the Workshop with the detailed procedure below or via the CLI after the previous commands.
First, click on Benchmark in the side menu:
Choose + Add an application, enter name and validate. Description field is optional.
Versions allow to compare different updates of the same application:
For an application, version number is often used (ex: 1.02.03)
For a website, the measurement date is often used (ex: 06_12_2023 with format dd_mm_yyyy)
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
Firefox is not available anymore for the moment. Sorry for the inconvenience.
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
Results
After the test is complete, the results are available in the dashboard tab, with a global Ecoscore from network and client resources grades.
Verify that all rules have been evaluated : 24 rules should be verified.
If it is not the case, re launch benchmark.
Launch with the CLI
It is possible to launch benchmark measures via the CLI. For that, the first configuration steps presented at the beginning of this page must be followed until the terminal selection.
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.
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