Initialize startup environment

Ask general questions here.
Posts: 4
Joined: Fri Feb 26, 2016 10:58 pm

Initialize startup environment

Post by ttnic » Thu Mar 10, 2016 12:39 am


I am a beginner in (Ranorex) test automation software so I have some basic questions for which I would need your advice:

- how to Initialize the startup environment
If I record multiple test scenarios independent from each other it is probably best if they are run from "clean" desktop. So I would like to repeat two steps: 1) Close all forms/applications 2) run recording
What is the best way to do "1) close all worms" or is there any other better way to prepare the startup environment ?

- can I run multiple recordings at the same time and how
Ranorex generates EXE files which can be run independently to execute test scenarios. So in order to run multiple tests at the same time I should a) run them on different computers b) create separate user accounts and execute EXE files as task scheduler jobs assigned to different users ?

- is automatic sending reports to e-mail supported
I would like to receive reports on testing results on mail if they fail. Does Ranorex support that kind of automation or should I read some files and send them by mail manually ?

Version: 5.4.5, evaluating
Windows 7

Thank you for the answers.

User avatar
Ranorex Guru
Ranorex Guru
Posts: 6529
Joined: Mon Aug 13, 2012 9:54 am
Location: Zilina, Slovakia

Re: Initialize startup environment

Post by odklizec » Thu Mar 10, 2016 8:27 am


All issues you have described are best to solve using virtual machines and continuous integration tool (e.g. Jenkins, Bamboo, etc...). I personally use a combination of Jenkins CI and VSphere VMs. With properly configured Jenkins job, you can schedule when and where the tests are running. Additionally, you can instruct VM to restart/restore VM snapshot to a default state, so you don't have to worry about changes made with previously running tests.

Jenkins can also send emails with success/failure message and some other useful details. You can for example define to whom to send email, based of the type of failure. And unlike of scheduled jobs (using windows scheduler), Jenkins can hold the jobs in stack and run them sequentially (start next job once the previous one is finished).

In other words, no, you can't run multiple tests at the same time (on the same machine). Not even with multiple user accounts because Ranorex needs realized desktop. And if you run your tests via windows scheduler (using multiple accounts), only one account will be actually visible and so your tests will fail if started on other accounts.

BTW, it seems the upcoming major version of Ranorex should bring us some of the Continuous Integration functionality so it may be possible to run tests on multiple machines directly from Ranorex environment (without using 3rd party tools like Jenkins). But I think this new Ranorex functionality will never fully replace tools like Jenkins.

If you are interested to learn more about Ranorex integration with CI tools, check the Ranorex blog articles available here:

Hope this helps?
Pavel Kudrys
Ranorex explorer at Descartes Systems

Please add these details to your questions:
  • Ranorex Snapshot. Learn how to create one >here<
  • Ranorex xPath of problematic element(s)
  • Ranorex version
  • OS version
  • HW configuration

Posts: 4
Joined: Fri Feb 26, 2016 10:58 pm

Re: Initialize startup environment

Post by ttnic » Thu Mar 10, 2016 2:04 pm

Thank you for the answer It helped a lot.

So in order to record test scenarios on one machine and run them on another (virtual) I would need to buy one Premium Node-Locked license and one Runtime license ?

User avatar
Support Team
Site Admin
Site Admin
Posts: 12169
Joined: Fri Jul 07, 2006 4:30 pm
Location: Houston, Texas, USA

Re: Initialize startup environment

Post by Support Team » Fri Mar 11, 2016 1:10 pm

Hello ttnic,

Yes, you are correct. In order to create tests you would need a Premium Node-locked or Premium Floating license. If you want to execute tests on dedicated machines, a Runtime Floating license is sufficient.

Detailed information about the different types of licenses can be found at our website.

If you need more information, please do let me know.