Path Editor Basics

The Path Editor is where you validate and refine RanoreXPath, so it reliably matches the UI elements you intend. It complements the Browser & results view: Browser & results show the live element tree and properties, while the Path Editor helps you tune the locator.

When to use the Path Editor

Use the Path Editor when:

• Your RanoreXPath matches too many elements
• A locator breaks after UI changes
• You want to replace an unstable attribute with a better one

Open the Path Editor and validate a path

1. Start Ranorex Spy (Integrated or Standalone).
2. Track an element so Spy generates a RanoreXPath.
3. Switch to the Path Editor view.
   
4. Confirm the status shows the expected number of matches (for example, “1 element found” vs multiple matches).

Change which attributes identify a node

When Ranorex tracks an element, it automatically chooses identification attributes. You can change those choices:

1. Track an element (example: a button in the demo app).
2. Click into the RanoreXPath line and switch to the Path Editor.
3. Select the node you want to refine (for example, the button node).
4. Check/uncheck attributes to replace an unstable attribute with a better one (example: deselect controlname and select controltext).
   The RanoreXPath updates automatically, and Spy reports the match count.

Tip: If your path matches multiple elements, add detail (attributes/predicates), or use indexing like [2] to disambiguate.

Understand what the Path Editor is showing

The Path Editor provides a visual representation of the RanoreXPath nodes (root → intermediate nodes → final node). This helps you see where wildcards were inserted and which nodes are fixed vs flexible.