Page Comparison

mode

The type of job you want to lauch, as explained above.

apk or custom or url or freerunner

greenspector

This block contains details about the GREENSPECTOR application in which you want to save your measures.

application

name

The name of the application .

version

The version of the application.

job

The job definition.

url

If you previously set mode to url, it is the URL of the website you want to measure.

Otherwise it is an URL pointing to your Android APK.

You can precise a local path to your apk, a public URL to download your apk, a package name if you want to benchmark an already installed apk or a package name if you want to install from the PlayStore before running the test

You can choose an URL :

• local path : /home/user/app/demo.apk

• public URL : https://dl.greenspector.com/demo/demo.apk

• package name : com.microsoft.office.outlook

urls

You can provide a list of APKs to be installed and eventually measured.

You can precise a local path to your apk, a public URL to download your apk, a package name if you want to benchmark an already installed apk or a package name if you want to install from the PlayStore before running the test

When using custom mode at least one of the APK should contain your instrumented tests (if you do not use tests written in Greenspector DSL with the option testsSuites)

for each url you can choose the location :

• local path : /home/user/app/demo.apk

• public URL : https://dl.greenspector.com/demo/demo.apk

• package name : com.microsoft.office.outlook

testPackages

If you previously set mode to custom, you can provide a list of packages containing your instrumentation test cases.

testsSuites

If you previously set mode to custom, you can provide groups of tests files writen with the Greenspector DSL.

For example :

testsSuites:
  - name: suite1
    testFiles:
       - "/home/user/test/steps1.testgb"
       - "home/user/test/steps2.testgb"
  - name: suite2
    testFiles:
       - "/home/user/test/steps3.testgb"

monitoredPackages

If you previously set mode to custom, you can provide a list of packages to monitor.

monitoredPackage

(Deprecated)

If you previously set mode to custom, you can provide the package to monitor. 

This field is deprecated, prefer to use monitoredPackages

extras

Use to transmit extras parameters to your instrumentation with the format key, value

• You can use predefined parameters :
  

  • config-skipsetupphone: if "true" then skip the setup configuration that happens before test.

  • config-waitForIdle: if "false" set idle timeout to 0
    

  • config-screenofftimeout: Set the time of inactivity before the screen goes to sleep (in millisecond)
    

  • config-screenbrightness: set brightness of the screen. value is between 0 and 255

  • config-gps: if "enabled" then activate location on phone before test

  • config-bluetooth: if "enabled" then activate bluetooth on phone before test

  • config-nfc: if "enabled" then activate NFC on phone before test

  • config-darkmode: if "enabled" then activate the dark mode on phone before test

• You can use custom parameters to fill parameters on your GDSL file

• You can filter your custom UIAutomator tests (no GDSL tests) using those extras parameters.

https://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner)

You can use custom parameters like this :

extras:
    PARAMETERNAME: "myValue"
will replace all ${PARAMETERNAME} in the GDSL file by myValue

If you use custom UIAutomator tests (no GDSL tests) you can filter the class you launch by annotation :

extras:
    annotation: com.greenspector.demo.test.MyAnnotation

(this extra parameter will be added to your uiautomator instrumentation like this -e annotation com.greenspector.demo.test.MyAnnotation)

networkMode

The networkMode of the test. The phone has to be able to handle the networkMode.

WIFI, 4G, 3G or 2G. Default value is WIFI.

scenario

Possible value is simple for an APK job. For a URL job, both simple and avance can be used.

APK job / simple scenario (deprecated) :

• Reference Measure (only the mobile platform) for 20 seconds

• Application Idle in foreground for 20 seconds

• Application Idle in background for 20 seconds

URL job / simple scenario (deprecated) :

• Reference Measure (only the browser) for 20 seconds

• Website Launch for 20 seconds

• Website Idle in foreground for 20 seconds

URL job / avance scenario:

• Reference Measure (only the browser) for 20 seconds

• Website Launch for 20 seconds

• Website Idle in foreground for 20 seconds

• Scrolling the Website for 4 seconds

• Website Idle in background for 20 seconds

simple (deprecated) or avance

iterations

How many times you want to run the scenario.

testTimeout

Timeout for the total duration of the test. Default value is 30m, max value is 60m.

45m30s

stepName

Name of the step

duration

Duration of the test.

1m30s

authentication

If you previously set mode to apk, the Test Runner can handle an authentication form if your application has one.

actions

Set of actions to interact with the authentication form, either by coordinates or by IDs.

There is currently two types of actions: click and text.

- "text;coordinates;300;400;user@mail.com"

- "text;id;session[password];userpassword"
- "click;coordinates;500;900"

browser

If you previously set mode to url, it is the web browser you want to measure on.

Only Google Chrome is supported for now.

chrome

cache

If you previously set mode to url, set this to true if you want the Test Runner to run a second test of your website with data in the browser cache.

online

Set this to true if you want the Test Runner to automatically send the results of the measures to your GREENSPECTOR Server. Otherwise, set it to false, the results will be saved locally.

modules

http_request

Set this to true to enable analysis of HTTP requests.

android_system_monitoring

Set this to true to enable collection of additional system metrics during the job.

hardware_probe

Set this to true to enable physical measurement  

wakelock_probe

Set this to true to enable wakelock measurement for the first iteration