S
Subbu2687
Hi Team,
We have nearly 30 Windows Server 2012 R2 AWS instances which are connected to a Jenkins Server (running in CENTOS AWS machine). The windows machines are used to run Selenium Test Automation scripts invoked from Jenkins server.
Objective:
Invoke full instance of Chrome browser through Chrome Driver and view Selenium script execution in Windows node.
Issue:
We connect AWS Windows instances to Jenkins server as Windows Service. Everytime when the scripts are triggered from Jenkins, chrome browser is invoked only in headless mode and does not invoke full instance of the browser. We identified that the windows service did not interact with the desktop and hence the browser got invoked only in headless mode.
We did enable "Allow service to interact with desktop" for the service and modified registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\NoInteractiveServices from 1 to 0. But whenever chrome browser is invoked for executing the scripts the "Interactive Services Detection" dialog appears and the script execution does not proceed further. Also, when we click on "View Message" button in the pop-up, it takes us to a completely separate screen on the desktop.
Kindly advice if there is a solution for seamless interaction of Windows Service with desktop and without the "Interactive Services Detection" popup?
Continue reading...
We have nearly 30 Windows Server 2012 R2 AWS instances which are connected to a Jenkins Server (running in CENTOS AWS machine). The windows machines are used to run Selenium Test Automation scripts invoked from Jenkins server.
Objective:
Invoke full instance of Chrome browser through Chrome Driver and view Selenium script execution in Windows node.
Issue:
We connect AWS Windows instances to Jenkins server as Windows Service. Everytime when the scripts are triggered from Jenkins, chrome browser is invoked only in headless mode and does not invoke full instance of the browser. We identified that the windows service did not interact with the desktop and hence the browser got invoked only in headless mode.
We did enable "Allow service to interact with desktop" for the service and modified registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Windows\NoInteractiveServices from 1 to 0. But whenever chrome browser is invoked for executing the scripts the "Interactive Services Detection" dialog appears and the script execution does not proceed further. Also, when we click on "View Message" button in the pop-up, it takes us to a completely separate screen on the desktop.
Kindly advice if there is a solution for seamless interaction of Windows Service with desktop and without the "Interactive Services Detection" popup?
Continue reading...