GUI Functional tests fail when running on our OPL. It appears the proxy issue is associated with the Chrome_85.0.4183.83:2.7.7 image.
Test Execution Result: FAIL
• gcr.io/verdant-bulwark-278/blazemeter/v4:1.20.92-slim
• gcr.io/verdant-bulwark-278/blazemeter/charmander/chrome_85.0.4183.83:2.7.7
Test Execution Result: FAIL
• gcr.io/verdant-bulwark-278/blazemeter/v4:1.20.98-slim
• gcr.io/verdant-bulwark-278/blazemeter/charmander/chrome_85.0.4183.83:2.7.7
Test Execution Result: PASS - https://a.blazemeter.com/app/#/accounts/xxxxxxx/workspaces/xxxxxxx/projects/xxxxxxx/masters/xxxxxxx/details/video
• gcr.io/verdant-bulwark-278/blazemeter/v4:1.20.92-slim
• gcr.io/verdant-bulwark-278/blazemeter/charmander/chrome_85.0.4183.83:2.6.7
Test Execution Result: PASS - https://a.blazemeter.com/app/#/accounts/xxxxxx/workspaces/xxxxxxx/projects/xxxxxx/masters/xxxxxxx/details/video
• gcr.io/verdant-bulwark-278/blazemeter/v4:1.20.98-slim
• gcr.io/verdant-bulwark-278/blazemeter/charmander/chrome_85.0.4183.83:2.6.7
We noticed the OPL was running an older release of taurus-cloud image, which does not support special characters in the proxy password. We upgraded the taurus-cloud image from version 92 to 98 hoping this would correct the issue, but the problem is still seen.
Release : SAAS
Component : BLAZEMETER FUNCTIONAL TESTING
The latest images of Charmander and Taurus, which improves proxy handling are:
You must also have the 'useSelenium4' feature flag is enabled on your account. If you aren't sure if the 'useSelenium4' feature flag is enabled, please open a support case and request that someone verify your account settings.