as mentioned in the headline, a short RF browser automation script works when running in cmd, but doesn’t if trying to run by using Jenkins. In cmd the automation works fine, means the browser opens physically and you can see the changes by automated clicks. But using Jenkins I get error messages and nothing opens physically.
This is the output using Windows cmd (+ browser automation works fine physically):
(Sorry, as a new user I just can upload 1 picture, but same result as shown under 2).)
And this is the output using Jenkins (+ no physically browser automation):
In the output with simple robot command, there are no rror messges, but when it runs triggered by Jenkins there is no physically browser automation as happens by using cmd. So, no browser opens, no automated clicking happens and so on. But on cmd it works like this. I don’t know whats wrong. Or do I have to use other Commands under Jenkins/Windows cmd?
Do you use the Jenkins robot plugin? And do you have an build step in which you go to the correct drive and directory? See this Youtube video for example.
How does that jenkins slave/node is started ? While this question may seem irrelevant, any type of GUI automation on windows slave/node is really really relevant.