Explore topic-wise InterviewSolutions in .

In general, there are no known incompatibilities. However, some antivirus or security software blocks CERTAIN Ranorex functionality. Consequently, if you EXPERIENCE problems with your automation and are RUNNING antivirus or security software, we recommend temporarily switching that software off for a TEST run.

In general, there are no known incompatibilities. However, some antivirus or security software blocks certain Ranorex functionality. Consequently, if you experience problems with your automation and are running antivirus or security software, we recommend temporarily switching that software off for a test run.

The FOLLOWING LINK to our online documentation shows what is NEEDED to develop or to simply run RANOREX tests.

The following link to our online documentation shows what is needed to develop or to simply run Ranorex tests.

Yes it is. Simply use the 'PerformClick' instead of the normal 'Click' METHOD when working with WEB adapters LIKE 'Div TAG', 'Input' or 'Link'.

Yes it is. Simply use the 'PerformClick' instead of the normal 'Click' method when working with web adapters like 'Div Tag', 'Input' or 'Link'.

YES it is. SIMPLY ensure that your SILVERLIGHT application does not run in window-less-mode, i.e. SET the 'Windowless' property of the Silverlight HTML object to false.

Yes it is. Simply ensure that your Silverlight application does not run in window-less-mode, i.e. set the 'Windowless' property of the Silverlight HTML object to false.

Ranorex provides the dedicated CLASS "PopupWatcher" to watch for and to handle POPUP windows. By using this class, not only simply click actions to close popup DIALOGS can be called. Even more COMPLEX scenarios can be HANDLED in custom callback routines being called at the time the popup appears.

Ranorex provides the dedicated class "PopupWatcher" to watch for and to handle popup windows. By using this class, not only simply click actions to close popup dialogs can be called. Even more complex scenarios can be handled in custom callback routines being called at the time the popup appears.

That's one of the BIG advantages of USING Ranorex. You're able to use your existing development environment to develop Ranorex based test automation CODE. Additionally the code GENERATED by the Ranorex Recorder or Ranorex Repository can easily be integrated into your VISUAL Studio projects.

That's one of the big advantages of using Ranorex. You're able to use your existing development environment to develop Ranorex based test automation code. Additionally the code generated by the Ranorex Recorder or Ranorex Repository can easily be integrated into your Visual Studio projects.

Yes, it is POSSIBLE to run AUTOMATED tests on runtime machines without Ranorex Installation. Please refer to the chapter XCOPY Deployment (Running tests without Ranorex Installation) in the USER GUIDE.

Yes, it is possible to run automated tests on runtime machines without Ranorex Installation. Please refer to the chapter XCOPY Deployment (Running tests without Ranorex Installation) in the User Guide.

The RESULT of a Ranorex test automation project is always an executable file. The GENERATED *.EXE can easily be STARTED from other ENVIRONMENTS supporting command line execution.

The result of a Ranorex test automation project is always an executable file. The generated *.exe can easily be started from other environments supporting command line execution.

Adapters provide an easy-to-use interface for accessing attributes and ACTIONS of ELEMENTS. Each item generated by the RANOREX object repository automatically represents a Ranorex Adapter (Button, CheckBox, Text, ListItem, TreeItem, ...). You can only create a Button Adapter of an element if the element supports the Button ROLE, i.e. if Ranorex Spy recognizes the element as a Button. 

If your controls are RECOGNIZED as 'Unknown' or 'Element', Ranorex cannot assign them a role. You can't use special attributes or actions with these elements, but you can usually still create a path that identifies the element to execute minimally mouse clicks.

Adapters provide an easy-to-use interface for accessing attributes and actions of elements. Each item generated by the Ranorex object repository automatically represents a Ranorex Adapter (Button, CheckBox, Text, ListItem, TreeItem, ...). You can only create a Button Adapter of an element if the element supports the Button role, i.e. if Ranorex Spy recognizes the element as a Button. 

If your controls are recognized as 'Unknown' or 'Element', Ranorex cannot assign them a role. You can't use special attributes or actions with these elements, but you can usually still create a path that identifies the element to execute minimally mouse clicks.

You can easily EXTEND standard recordings with USER specific code actions by CONVERTING existing action ITEMS or by adding a NEW user code action item to a recording.

You can easily extend standard recordings with user specific code actions by converting existing action items or by adding a new user code action item to a recording.

Especially with big files, the performance of MICROSOFT's default file format for excel spreadsheets is getting poor. This WEAKNESS might also affect your data driven test execution. For performance improvements you could use the binary file format (xlsb) instead of the default ONE (xlsx). Simply SAVE your Excel spreadsheet with the extension "xlsb" and assign it to your excel data source.

Especially with big files, the performance of Microsoft's default file format for excel spreadsheets is getting poor. This weakness might also affect your data driven test execution. For performance improvements you could use the binary file format (xlsb) instead of the default one (xlsx). Simply save your Excel spreadsheet with the extension "xlsb" and assign it to your excel data source.

Yes. RANOREX supports four different DATA CONNECTORS to build data driven test cases: 

• Simple Data Connector
• SQL Connector
• CSV File Connector
• EXCEL Connector

A general description of how to create data driven test cases can be found here.

Yes. Ranorex supports four different data connectors to build data driven test cases: 

A general description of how to create data driven test cases can be found here.

No. It's also POSSIBLE to search for GUI elements or forms USING a number of DIFFERENT 'Find' methods to search and/or FILTER for child elements.

No. It's also possible to search for GUI elements or forms using a number of different 'Find' methods to search and/or filter for child elements.

Yes. All IDENTIFICATION information is stored within a RanoreXPath expression and is therefore SEPARATED from the test automation code.

The following RanoreXPath expression finds a BUTTON both on Windows XP and on Windows Vista: 

/form[@title='WordPad']/.//button[@text='&No' or @text='Do&n''t Save'] 

The RanoreXPath SEARCHES for a button, whether it contains the text '&No' or 'Do&n''t Save'.

Yes. All identification information is stored within a RanoreXPath expression and is therefore separated from the test automation code.

The following RanoreXPath expression finds a button both on Windows XP and on Windows Vista: 

/form[@title='WordPad']/.//button[@text='&No' or @text='Do&n''t Save'] 

The RanoreXPath searches for a button, whether it contains the text '&No' or 'Do&n''t Save'.

RANOREX uses the RanoreXPath to identify applications and their UI elements REQUIRED for test automation. The RanoreXPath provided by Ranorex Spy consists of MANY different, technology dependent attributes which can be modified and adapted by the USER. To separate test code from identification information Ranorex provides a repository to map LOGICAL names to RanoreXPath expressions.

Ranorex uses the RanoreXPath to identify applications and their UI elements required for test automation. The RanoreXPath provided by Ranorex Spy consists of many different, technology dependent attributes which can be modified and adapted by the user. To separate test code from identification information Ranorex provides a repository to map logical names to RanoreXPath expressions.