Problems with versions of Devexpress in the repository

Technology specific object identification, supported applications, web technologies, and 3rd party controls.
Miguel
Posts: 2
Joined: Mon Sep 11, 2017 3:55 pm

Problems with versions of Devexpress in the repository

Post by Miguel » Mon Sep 11, 2017 5:03 pm

Hi everyone,

We have problems with the repository and the elements from Devexpress, we have some solutions with 600 test cases automated with ranorex and the aplications using any controls with devexpress version 14.1, the problem exist when we update the controls to version 16.2 of devexpress, the routes of the items in the repository change when the installed version of the devexpress is updated in the computers where the automation is being done, causing many items to no longer be recognized in the test cases, so it is a great inconvenience because, as I mention them, we have several solutions and a large number of test cases that need to be updated one by one for the test cases to work correctly, have any options to be able to update the repositories without the need to perform item by item? or exist any option for portability of repository when exist changes in the versions of the developers tools?

I attached one example of the changes in the paths of the repository,

With 14.1 version Devexpress
Devexpress_14.1.PNG
With 16.2 version Devexpress
Devexpress_16.2.PNG

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

Re: Problems with versions of Devexpress in the repository

Post by odklizec » Tue Sep 12, 2017 9:36 am

Hi,

I'm afraid, the images you tried to attach are not visible. But honestly, images are usually useless for the problem evaluation. Please post a Ranorex snapshot instead (both before and after) and ideally, also your test suite repository.

Anyway, if the elements' xpaths have changed after updating AUT with never devexpress, there is most probably no other way than to update the xpaths in repo. You see, Ranorex has no way to detect and update the changed xpaths automatically. If the repo is nicely constructed (with rooted folders), it may be relative easy task. But if the repo is messy, it may be somewhat complicated ;) But as mentioned, without seeing the snapshots (before and after) and actual repo, there is not much anyone here can do or suggest.
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

Miguel
Posts: 2
Joined: Mon Sep 11, 2017 3:55 pm

Re: Problems with versions of Devexpress in the repository

Post by Miguel » Wed Sep 13, 2017 5:00 pm

Hi,

I send you the screenshots

This with the version 14.1 of Devexpress
Devexpress_14.1.PNG
Devexpress_14.1.PNG (142.46 KiB) Viewed 476 times
This with the version 16.2
Devexpress_16.2.PNG
Devexpress_16.2.PNG (152.68 KiB) Viewed 476 times

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

Re: Problems with versions of Devexpress in the repository

Post by odklizec » Thu Sep 14, 2017 7:29 am

Hi,

As mentioned before, screenshots are not useful here. Please post Ranorex snapshots!

However, as discussed in other posts, related to devexpress, there is no way around updating the xpaths, when devexpress changes the GUI structure. You simply have to update the xpaths in repo. Your only hope is to use rooted folders wherever possible. So then it should be easy for you to update the xpath of just rooted folders, instead of all repo items. Also, you can try to use the approach mentioned here:
https://www.ranorex.com/forum/post45698.html#p45698
But this may slow down the element search.
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