Update KendoUI

Ask general questions here.
MB_wiko
Posts: 85
Joined: Fri Sep 09, 2016 1:05 pm

Update KendoUI

Post by MB_wiko » Mon Feb 20, 2017 2:49 pm

We use KendoUI for our web application. Last week we installed the new KendoUI Update and some paths changed. So Ranorex didn't find the elements. An example follows:

old path
span[@ID=Insertedbox]/span/span[2]/?/?/button

new path
span[@ID=Insertedbox]/span/span[3]/?/?/button

So I updated all the pathes in repository manually, I searched them with Crtl.+F and repleced the old path with new path. The function find and replace didn't work in repository. This process is time consuming. KendoUi is a framework with a high market share. So we think also other customers of Ranorex has this questions with KendoUI updates and perhaps some better solutions. It is a general question how to handle with KendoUI Updates, without reprogramming Ranorex.

The ID is on a very high level, our developers says, that we can not move them to the last level, to the element button. This way is no solution for us.

Perhaps someone has a better solution to handle KneodUI updates or some experiences.

Thanks a lot in Advance for your answers.

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

Re: Update KendoUI

Post by odklizec » Mon Feb 20, 2017 3:02 pm

Hi,

Please upload a Ranorex snapshot (not screenshot) of the problematic element. Without snapshot, there is almost nothing we can do or suggest to you.

Basically, element indexes are the most fragile part in element identification. Ranorex offers them in case there is really no other reasonable ID available. However, there still may be a way to identify elements via other elements or simply by using an element attribute, which Ranorex considered not unique enough. Sometimes it's enough to edit the xpath weight, sometimes it's required manual editing of each recorded xpath. And in some cases, indexes are really the only available way how to identify some elements. In this case, you will have to update your repo each time the GUI has changed. Therefore, it's better to reduce the usage of indexes at bare minimum ;)
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