Page 1 of 1

Scheduling Ranorex script execution - Tools ?

Posted: Tue Feb 09, 2016 1:26 pm
by Zee357
I am running my Ranorex .EXE automation scripts on a VM in an automated/scheduled way daily. Or trying to plan for that.

What tool (Task Scheduler ?) is best on Windows Server 2008. I've heard of Jenkins, but we're not using that for anything else such as builds. It is only to schedule and execute the Ranorex built scripts; that is all.

I might want to convert my .Rxlog files to .PDF's after the execution of the scripts completes as an additional step as part of daily job.

Thanks.

Fred Zimmerman
Washington D.C.

Re: Scheduling Ranorex script execution - Tools ?

Posted: Tue Feb 09, 2016 4:01 pm
by odklizec
Hi Fred,

Jenkins is a perfect solution of your problem. If you are already using Jenkins for building, then you just have to add one additional step to run the test. There is a nice instructive blog post about integrating Ranorex with Jenkins...
http://www.ranorex.com/blog/integrating ... on-process
You can of course add also PDF conversion step at the end of test. Just add another step using ReportToPDF.exe tool (and some parameters) as described here...
http://www.ranorex.com/blog/ranorex-rep ... conversion

Re: Scheduling Ranorex script execution - Tools ?

Posted: Wed Feb 10, 2016 2:51 pm
by krstcs
I would agree with Pavel. Jenkins is what I use, even though my devs doen't use it anymore. It's free and pretty easy, where most other CI systems charge for every agent/slave system you connect to the server. I have 9 slaves right now, which allows for many more tests to run in the same time frame as a single test would.

As for PDF, you can use the converter, but... Did you know that the Ranorex Report is actually an HTML document named *.rxlog and an XML data document named *.rxlog.data??

If you rename them to *.html and *.html.data you can view then in a browser. And, you can host them on Jenkins as web pages, with the HTML Publisher plugin, and anyone can see them by going to the Jenkins server and checking the build results. This is what I do, and it works wonderfully. There's no need for extra steps in converting the documents, and you don't have to rely on anyone having to have a PDF reader (although they are built into most browsers now...).