This page provides details about the impact of updating the current browser version to headless Chrome Version 86.
- Chrome version 86 is available for:
- SaaS Controllers
- On-premise Controllers >=21.4.x with Synthetic Server >=21.4.1
Jobs in AWS locations get executed in Linux-based agents with Chrome version 86
Jobs in Azure locations get executed in Windows-based agents with Chrome version 86
The behavior changes described on this page are not applicable for the agents in Azure locations
fullscreen_window commands are not supported because of a bug in Selenium ChromeDriver for headless Chrome.
set_window_size() command instead of
Headless version includes major security enhancements and changes in the browser engine that results in increased page load time and session duration.
Some Python based Selenium scripts that run successfully in Chrome version 64 fail with "Script broken" error in Chrome version 86. This happens due to incompatibility between the Selenium commands and the latest Chrome web-driver.
Current Behaviour: Sessions with 4xx errors are not treated as client errors in certain cases
No action required.
Headless Chrome does not support extensions or embedded PDF viewer. The PDF is downloaded and viewable in resource waterfall but screenshot is not present. Hence, you can verify the availability of a PDF file but cannot take a screenshot.
You can verify the availability of the PDF document by sending an HTTP request using Python request library and assert on the response code.
Following is a sample script:
During multi-tab script flows, if the new tab is triggered indirectly, such as by an element click, the initial resources do not get captured in the new tab.
This occurs because of a puppeteer bug.
|Open the tab directly in the script and perform any operation.
Agent Machine Configuration
|Machine configuration: 2vCPU 8GB RAM
The page load time and session duration might increase.
Job Execution Environment
|Jobs are executed in Windows environment.
|Jobs are executed in K8S based Alpine containers.
If the website serves content based on operating system (OS), the scripts created based on windows environment fail.
Update the scripts with Linux environment based content.
Scripts fail with 4xx error in some cases.
This issue might occur when the server denies access to Linux agents or when website access is restricted only in Windows environment.
Provide access to Linux agent.
Update the IP whitelisting based on the IP addresses mentioned at Synthetic Hosted Agent.
The jobs with OS or file system based commands fail.
As per AppDynamics security standards, jobs are executed in stateless environments meant only for the execution of web tests. Hence, OS/file system based commands are not supported.
If you have used OS or file system based commands in your scripts, remove those commands.
|Network throttling feature is implemented using a third party library.
|Network throttling is implemented using Chrome browser dev tools protocols.
Either increase the timeout value or re-configure the throttling speed of the job.