Ranorex queries

Ask general questions here.
Posts: 28
Joined: Fri Aug 10, 2018 5:51 am

Ranorex queries

Post by Santhosh » Mon Feb 04, 2019 6:53 am

Hi Team,

Can anyone help me with below doubts:

1. How to provide the relative paths of executable files in “Run Application” command. Passing dynamic paths in launching some application ? [Hardcoded paths will not run on all environments ]
2. We have WPF based simulators in our automation environment. One simulator control are recognize using “WPFOnly” Setting where as another simulator get recognize using “UiaOnly” option, But my testcase uses both the simulators. How can we change the Setting of recording from WPFOnly to UiaOnly at the run time ?
3. How to access the common recording module across projects ? recording module create a copy of recording if we access in another project and changes done at one place will not reflect in other projects? How to handle the case, if I want to share “Login to Application” recording module common.
4. How to handle IF-ELSE conditions in testcase steps ? if I have scenarios to perform one steps and based on its outcome do step2 or step 3, how that decision making can be automate in Ranorex. ?

Thanks in advanced.

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

Re: Ranorex queries

Post by odklizec » Mon Feb 04, 2019 8:45 am


1) You will have to either pass the correct path via command line (via test suite global parameters), or simply obtain and fill the path to variable in runtime, via user code and then simply use that variable in Run command (or elsewhere required).

2) You may find useful this post...

3) This should help...
https://www.ranorex.com/blog/organizing ... est-suite/

4) Test Suite/Case conditions are very well described here:
https://www.ranorex.com/help/latest/ran ... ons-rules/
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