...
| 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 On these cases, you need to download chrome 110 archive which is suitable for your device |
...
| Panel | ||
|---|---|---|
| ||
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 | ||
|---|---|---|
| ||
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 | ||
|---|---|---|
| ||
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