The path editor | Ranorex
HomeUser GuideRanorex Studio AdvancedRanorex SpyThe path editor

The path editor

This section introduces and explains the path editor – one important part of Ranorex Spy. The path editor is where you specify and edit the RanoreXPath of tracked and identified UI-elements.

In this chapter

    Starting path editor from within Spy

    The path editor can easily be accessed from within Spy by simply selecting it in the working environment selector area.

    Accessing path editor from within Spy

    Accessing path editor from within Spy

    Select a UI-element in the browser tree view
    Click the PATH EDITOR link of the working environment selection
    See the changed path editor view with the selected UI-element in the tree view section

    Starting path editor from within Studio

    Any repository item in Ranorex Studio can be opened for editing in Spy. Here is how to do this.

    Accessing path editor from within Studio

    Accessing path editor from within Studio

    Select a repository item in the repository of Ranorex Studio
    Either click the EDIT IN SPY button of the repository item, or
    open the context menu and click Edit in Spy…

    Element could not be found

    If you open a repository item for editing in Spy there might be the problem that the corresponding UI-element could not be found by Spy. This may happen if the application hosting the UI-element is not started.

    Initial situation

    Could not find element error

    Could not find element error

    Select a repository item in Ranorex Studio
    Click the EDIT IN SPY link to open the repository item in Spy
    See Spy with the element tree indicating that the UI-elements have not been found in case the application under test is not started

    Important to know:

    The red symbols indicate that the corresponding UI-elements have not been found
    A status message at the bottom of the Spy window informs you about not finding the UI-elements

    Solution:

    Solution to UI-element not found error

    Solution to UI-element not found error

    Open the application hosting the corresponding UI-elements
    Click Refresh to update the references to the UI-elements

    Path editor working environment

    The path editor working environment consists of 4 basic areas and one important status message.

    Path editor working environment

    Path editor working environment

    Track button & RanoreXPath information. The track button is used to track, identify and add new UI-elements whereas the RanoreXPath edit line displays their unique specification and is used for editing the RanoreXPath
    Switch between UI-element browser tree and the path editor
    Tree view section: displays the components of the RanoreXPath specification in a tree-like structure
    Attribute comparison section: List of available UI-element attributes and their values with the option to select attributes to change the RanoreXPath specification accordingly
    Current UI-element identification status: informs if and how many UI-elements are identified by the current RanoreXPath specification

    Locked tree levels

    The root element of the UI-element browser tree of Spy limits the tracking and editing. All tree elements (i.e. parts of the RanoreXPath specification) above the root element of the UI-element browser tree are locked with respect to tracking and editing.

    Opening path editor from Spy

    Locked path editor tree level - part I

    Locked path editor tree level – part I

    The root element RXMainFrame in the Spy browser tree …
    …represents the root element in the tree view section of the path editor

    Important to know:

    No element above the current root element can be tracked nor edited. In the current example, no tracking and editing beyond the application being referenced by the repository item RXMainFrameare possible.

    Opening path editor from Ranorex Studio

    Any repository item can be edited in Spy with the path editor by clicking the corresponding button in the repository.

    Locked path editor tree level - part II

    Locked path editor tree level – part II

    This is a basic userguide text with all paddings and margins set correctly. Just use all text styles H2, H3 etc… as you want. If you need to define Key strokes like CTRL do it like this here.

    First you need to…
    One way to do it is…
    In the first section you see..