| Status | ||||
|---|---|---|---|---|
|
...
This command will tell you whether your basic configuration and credentials are correct or not. If correct, you should have the message "Server pinged with success".
Optional proxy configuration
| Info |
|---|
The proxy can be automatically detected. In windows, the Test Runner automatically detects In linux or mac, the Test Runner automatically detects env variable |
If previous gspt ping does not work in your work office, you probably need to configure a proxy to allow the CLI to access Internet.
...
7 - --extra: Use to transmit extras parameters to your instrumentation with the format name=value (ie --extra annotation=com.greenspector.demo.test.MyAnnotation add the following parameters to your instrumentation -e annotation com.greenspector.demo.test.MyAnnotation). Thus you can filter your tests for example using those extras parameters : https://developer.android.com/reference/android/support/test/runner/AndroidJUnitRunner). It can also be used to fill parameters on GDSL file. (exemple --extra PARAMETERNAME="value" will replace all ${PARAMETERNAME} in the GDSL file by value). Optional
8 - --networkMode: The network mode for the test. Values can be "WIFI", "4G", "3G" or "2G". (Default: WIFI). Optional
9 - --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 you don't need these metrics, you can disable this iteration, it will reduce testing time.
10 - --only-dumpsys: Run only a Android System Monitoring iteration. This iteration will only be able to retrieve Android System metrics (Views, Activity, OpenSSL Sockets, ...).
Some options are deprecated:
...