Page Comparison

Problem

Message :

• Please set the application name in .greenspector/config.yml to use this feature

• Please set the version in .greenspector/config.yml to use this feature

...

Complete the file .greenspector/config.yml with the missing information by looking at the CLI usage section..

...

If you activated the http_request module, it’s possible you encounter an error of this kind.

...

From here, you need to add Phantomas Path and version in your config.yml, then relaunch the Testrunner.

...

...

Results are not displayed on the web interface after measures have been run.

...

1. In your browser, https://your-instance.greenspector.com/api must return OK.

2. If your measures were run using the Test Runner, verify that your measures were not done in offline mode by checking your .greenspectorconf.json file. In that case, simply fix your configuration. Moreover, you can send your previous measurement results using the CLI.

...

Problem

Error: Unauthorized. Your token may be invalid. Please check your configuration file.

Reason

...

: This message appears when you are trying to use a feature that requires connection and your private token is not valid.

...

1. Verify your token and server address in [USER HOME]/.greenspector/config.yml

2. Check your connection using the command gspt ping.

...

The PC-Launcher used by the Testrunner to measure Websites on PC relies on Bash.exe. We support the Git Bash Implementation provided by Git for Windows. If you use another Bash implementation, you may encounter some issues while measuring a Website. which are, the browser getting stuck for more than a minute on a blank page with URL field set as "data;" and the Testrunner stuck on the following

...

If that’s the case, please ensure you are compliant with our requirements and update your Bash implementation.

...

...

When I try to run the CLI , I get a command not found error.

...

If the gspt command is not found by your system, check if the path to the GREENSPECTOR Command Line executable file is in the $PATH.

7 - Chromedriver issue on Windows

While doing website measures on Windows, chromedriver processes may stay open and accumulate after the Testrunner exited and disturb further use. You may need to kill those processes.

8 - Firefox browser is not supported for standard URL jobs on mobile

When launching a standard URL job on mobile with the Test Runner, only Chrome browser is supported. If you set Firefox browser in the job configuration file, the Test Runner may not fail with an error indicating that the browser is not supported.

...

Meter tools running on PCs or servers (Meter API Java and JS, Meter Standalone, TestRunner, Plugin JMeter) can be used:

...

They are not validated in distant mode (via SSH) from a Windows-based PC to a Linux- or Windows-based server.

...

...

It's likely that your network requires a proxy to access the Internet. For example, it may work at home, but not at the office. To make sure it's your corporate network that's doing the blocking, you can do a connection share with your phone so that your PC no longer uses your office network, and re-run the 'gspt ping' command. If the ping command still doesn't work, the problem is elsewhere. If the ping command works, you'll need to configure the CLI with the proxy.

The documentation to configurate the proxy for the CLI is here : https://greenspectorstudio.atlassian.net/wiki/pages/createpage.action?spaceKey=DOCUMENTATION&title=CLIx/hoDKBw in “Optional proxy configuration” part.

...

...

Example :

...

If you have the same problem, go to the phone in settings / apps, choose the Greenspector application, in Permissions / Files and media, choose 'Allow management of all files'. Do the same for the application com.greenspector.testbench.launcher.android.test

...

...

On rooted device (like s9 on our TestBench), you can’t pass spaces in extras parameters values.

...

# Testrunner job configuration file
mode: custom # apk | url | custom
greenspector:
  application:
    name: Myapp # Your application's name
    version: "1" # Your application's version 
job: # Custom job android apk
  testsSuites:   
    - name: suite1
      testFiles:
        - "../dsl/testdsl.testgb"
  monitoredPackages: 
    - com.android.chrome # The package to monitor, existing or newly installed
  iterations: 1 # Number of iteration for each test case
  extras:  
    config-screenbrightness: "127"
    step1: "step1 with space" #space do not work on rooted device
    config-skipsetupphone: "false"
  testTimeout: 30m0s # Timeout for the total duration of the test, default value is 30m, max value is 60m
  online: true # [true, false]
  networkMode: WIFI
  modules:
    android_system_monitoring: false
    tcpdump: false

...

In bash, the ! is interpreted. For example the command ‘!u' attempts to execute your last command starting with u. When using the CLI, if you must use a ‘!’ in your additional parameter you need to escape it with '\’.

gspt testbench custom-tests --testsSuite launch:./script.testgb --monitoredPackage "com.android.chrome" --iterations=1 -e PAUSEDURATION=30000 -e PAUSEAFTERLOAD=1000 -e PSWD="onepassword\!"

14 - Website GDSL tests behavior may differ between local device and Test Bench device

When automating your user journey, sometimes a GDSL test will pass on a local device and fail on a Test Bench device or vice versa. Test results may show that there are differences in the dump, the text may be found in the Test Bench device dump and not in a local device dump.

This behavior probably comes from the fact that the local device and the Test Bench device do not have the same Chrome version. Please install chrome 110 on local device https://greenspector.atlassian.net/wiki/spaces/DOCUMENTATION/pages/3121184771

...

WARN[2024-09-16T11:14:05+02:00] Could not reinstall the APK correctly. Will uninstall first...
INFO[2024-09-16T11:14:05+02:00] ADB - Uninstall com.greenspector.testbench.launcher.android
ERRO[2024-09-16T11:14:06+02:00] could not uninstall apk: Error: Exit code error: 1
- Command: adb -P' '5037' '-s' '68ce37c6' 'uninstall' 'com.greenspector.testbench.launcher.android
- Stderr:
  Stdout: Failure [DELETE_FAILED_INTERNAL_ERROR]

If you have this error when launching a test with the TestRunner, please read the following :

...

...

...

testrunner -c config.yml cleandevice