I have windows node attached to Jenkins. All robot scripts are running on Jenkins windows node in headless mode… i tried to install selenium grid n tried to open the browser using remote url option by giving hub url… but i am facing issues.can pls help me in understanding how to see gui execution.
There are any questions in your question. You should have given much more information. We can only try to guess your setup, and to help we might go on a wrong way.
For starters:
How can you run the same test in the Windows node?
Can you login into the Windows node (to see its Desktop) with the same credentials the Jenkins job is using?
You mention “headless mode”, this means that no visual output will be shown even if running locally. Did you tried to not run headlessly?
I have Jenkins server where windows agent node is configured as slave. i am running robot test on remote windows agent node in headless mode.
I would like to know, any way if I trigger the execution on remote windows from Jenkins, can I see the live execution happening.
Fyi. I did not try logging in to windows node with credentials Jenkins uses to trigger the job
If it fails, it may indicate that the Windows node, is not configured to normal browser mode.
(this could be because the way Windows node is connected to Jenkins. To have GUI capabilities, it must be connected with the Java client/agent, and not as a Windows service)
3.You must really access the Windows machine to see the Jenkins job run when not in headless mode. The Windows node would probably have the RDP (Remote Desktop) configured for access. Other possibility is to have a VNC server for you to access. You must understand that you need to be in the same login session that Jenkins is.
You mentioned Selenium Grid. This should be the best solution, because it probably includes a NoVNC access to the node. Maybe troubleshooting this setup would be the best.
FYI - And if the windows version is “Server” then when you use RDP make sure you use the /console option when connecting the RDP, otherwise you won’t see windows sent to the desktop. Windows servers have 3 desktop sessions by default, the one shown on the monitor and 2 for remote admins, but can have more if terminal services are running. /console is used for connecting to the desktop session shown to the monitor.