Ranorex tests errors as part of a Jenkins job.

Bug reports.
Posts: 1
Joined: Fri Dec 27, 2019 11:19 am

Ranorex tests errors as part of a Jenkins job.

Post by PhilJotham » Thu Jan 02, 2020 1:34 pm

I'm trying to set up a simple Jenkins job running a very simple Ranorex v9.1 test (proving 2+2=4 using Windows calculator!) - the Jenkins instance is just a simple "master" (i.e. no "slaves") running on a Windows 10 VM.

Unfortunately every time the Jenkins project executes I encounter a "This operation requires an interactive window station" error. This error does not occur if the same test is executed directly through Ranorex Studio OR through running the test executable directly on the VM that Jenkins runs on - so the error seems specific to running the test under Jenkins.

The relevant details of the Jenkins output are included below
*************Start of Ranorex Summary*************
Current Plugin version: 1.0.2
Ranorex Working Directory: E:\Jenkins_Workspace\Test Jenkins Projects\Ranorex Calc Test\CalcTest\bin\Debug\
Ranorex test suite file: \CalcTest\bin\Debug\CalcTest.rxtst
Ranorex test exe file: CalcTest.exe
*************End of Ranorex Summary*************
[2019/12/24 13:43:07.626][Debug ][Logger]: Console logger starting.
[2019/12/24 13:43:07.929][Failure][TestSuite]: This operation requires an interactive window station
[2019/12/24 13:43:07.958][Debug ][Logger]: Console logger stopping.
Build step 'Run a Ranorex test suite' changed build result to FAILURE
Finished: FAILURE

As far as I can tell I've configured the Jenkins job EXACTLY as per the example given in the webinar on this subject - so I'm baffled as to why it won't work. Any help/suggestions much appreciated :-)

Posts: 297
Joined: Thu Feb 23, 2017 10:37 am
Location: Benedikt, Slovenia

Re: Ranorex tests errors as part of a Jenkins job.

Post by McTurtle » Thu Jan 02, 2020 2:20 pm

Hello PhilJotham,

You might have followed the job configuration instructions exactly, but you seem to have missed the part that explains that you cannot start Jenkins as a service. Disable the service and start the Jenkins master as a process as explained here: Jenkins as process

Also, make sure that there is a user session open on the machine where the test is running.