Using Jenkins to automatically compile and launch a Ranorex 7.0 exe in a Win 8.1 x64 VM
It's the first time I get all the screenshots in the report completely black.
Screensaver was disabled in the VM, and also the VM is configured to never lock.
Can someone help me ?
Best regards,
Olivier
Report.Screenshot shows Black screen in VM
Re: Report.Screenshot shows Black screen in VM
is Jenkins being run as a process or as a service? Is your test being run as a process? Your test needs to be run as a process so that it may properly interact with the desktop environment.
"As Jenkins or the nodes executing the CI jobs normally are started as Windows services, they do not have sufficient rights to start UI-applications.
Please make sure that Jenkins as master and its slave nodes, where the Ranorex automation should be triggered, are not started as a service."
source: https://www.ranorex.com/blog/integratin ... n-process/
This link may also be helpful:
https://stackoverflow.com/questions/162 ... h-commands
"As Jenkins or the nodes executing the CI jobs normally are started as Windows services, they do not have sufficient rights to start UI-applications.
Please make sure that Jenkins as master and its slave nodes, where the Ranorex automation should be triggered, are not started as a service."
source: https://www.ranorex.com/blog/integratin ... n-process/
This link may also be helpful:
https://stackoverflow.com/questions/162 ... h-commands
Re: Report.Screenshot shows Black screen in VM
Thanks a lot for your answer !
Jenkins is not used as a service.
I tried to set up Ranorex plugin but got some issues as Jenkins is on a Debian server and java 8 is not yet supported by Debian.
Jenkins is not used as a service.
I tried to set up Ranorex plugin but got some issues as Jenkins is on a Debian server and java 8 is not yet supported by Debian.
Re: Report.Screenshot shows Black screen in VM
What happens when you run the test in this environment without Jenkins? Just directly running the test within the same VM environment. Have you watched the test execute? What kind of permissions is the test being executed with?