Recorded RxPaths are randomly split into base and relative

Ranorex Spy, Recorder, and Studio.
torlin
Posts: 8
Joined: Mon Feb 02, 2009 2:05 pm

Recorded RxPaths are randomly split into base and relative

Post by torlin » Mon Feb 02, 2009 2:23 pm

When I recorded a test of a web page and checked for the value in two table cells located side-by-side I found that Ranorex had put the two td tags in two different folders in the Global Repository. The two folders had different base RxPaths, the first one being considerably longer than the second one. The two elements' relative paths were also of different length, the first one much shorter. Combining the base path and the relative path to an absolute path for each element showed that they differed only in the last tag (being "/td[2]" and "/td[3]" respectively), just as expected.

Why were not the two elements placed in the same folder in the Global Repository?

In general Ranorex seems to split absolute paths rather randomly. Are there any rules that Ranorex follows and which I have not yet discovered?

User avatar
Support Team
Site Admin
Site Admin
Posts: 11709
Joined: Fri Jul 07, 2006 4:30 pm
Location: Graz, Austria

Post by Support Team » Mon Feb 02, 2009 6:37 pm

The general rule is that Ranorex tries to group two elements together if they share a common parent which makes 'sense' as a container e.g. a div tag

If I understand the case you described correctly, you have something like this:

item path= /a/b/c

first folder = /a/b, first item = c
second folder =/a, second itm = b/c

If that's true, those two items *should* be placed into the same folder.

We will have a look at your problem. A simple example where this is reproducible would be quite helpful.

Michael
Ranorex Team

torlin
Posts: 8
Joined: Mon Feb 02, 2009 2:05 pm

Post by torlin » Tue Feb 03, 2009 9:38 am

Sorry*, I have not been able to reproduce the problem. Therefor I can not provide a script for your further investigation.

* No, to be honest, I am not sorry. The problem is no longer there...