Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleCase 2 : use Test Runner to do the measurement

If you want to do measurement with your own phone or have the same configuration as the phones in the test bench, you will probably need to install a compatible version of Chrome with all GDSL commands : chrome 110.

To change chrome version on your phone on android 10+, you can do

  • Close your Chrome on your device

  • Download the mandatory library for chrome 110 trichrome-library

  • Connect your phone to your PC

  • Open a terminal on the directory where you download the apk and enter the command (if you have difficulty, please use completion to let your terminal set the correct path to the apk)

    Code Block
    adb install com.google.android.trichromelibrary_110.0.5481.65-548106533_minAPI29\(arm64-v8a,armeabi-v7a\)\(nodpi\)_apkmirror.com.apk
  • Download the .apkm bundle of chrome 110 here : chrome 110

  • Unzip the .apkm file

  • Connect your phone to your PC

  • Open a terminal on the unzip directory

  • Enter the command

    Code Block
    adb install-multiple -r -d *.apk
  • Open chrome on check it works

  • You need to prepare your chrome to use GDSL commands

    Code Block
    testrunner testdslcommand -c browserReset
Info

If the chrome 110 installation does not work, you probably have a phone with android <10 or your phone does not have a processor arm64-v8a. You can check with the command adb shell getprop ro.product.cpu.abi

On these cases, you need to download chrome 110 archive which is suitable for your device

Note

In this tutorial, we suggest to use apkmirror. Greenspector cannot be held responsible in the event of a security problem. We can only say that apkmirror is a good alternative to playstore with a serious community. Only community member can publish on the store, you just install an apk with the same signature as your chrome (the command ‘adb install’ will detect if the apk was not signed by google)

See https://greenspectorstudio.atlassian.net/wiki/spaces/DPP/pages/179601417/Troubleshooting+web#3---How-to-change-chrome-version-to-chrome-110-on-local-device-%3F

...

Panel
bgColor#FFEBE6

3 - How to change chrome version to chrome 110 on local device ?

...

Info

If the chrome 110 installation does not work, please check if you use the good archive for android 10+ or android <10. If it does not work, you probably have a phone which does not have a processor arm64-v8a. You can check with the command adb shell getprop ro.product.cpu.abi

On these cases, you need to download chrome 110 archive which is suitable for your device

All archives for chrome 110

...

Panel
bgColor#FFEBE6

4 - 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.

...

Panel
bgColor#FFEBE6

5 - 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.

...

Panel
bgColor#FFEBE6

6 - 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 Install Chrome 110 on local device