Page 1 of 1

Experience regarding Repository Maintenance

Posted: Fri Jan 14, 2011 11:20 am
by chfischer
I am evaluating Ranorex for our company's new flex based products and it looks really promising.

However, there are have a few concerns regarding the maintainability of the Elements Repository. The development of our new flex application is just starting and the chances that there will be fundamental changes in the gui are very high. So my question is, how do you maintain your Repository Items? Is there a best practice?

e.g Is it possible to change, let's say, a xpath "address" of a advancedDataGrid item and have all the corresponding cell items changed accordingly? or how do you test content in grids in a flexible way?

Regards,
Christian

Re: Experience regarding Repository Maintenance

Posted: Fri Jan 14, 2011 1:59 pm
by Support Team
Hi,
chfischer wrote:o my question is, how do you maintain your Repository Items? Is there a best practice?
Please take a look to following link http://www.ranorex.com/blog/organizing- ... rex-studio
Maintenance of the repository depends on your structure. You can create parent folders and logical folders to split up your repository.
chfischer wrote:e.g Is it possible to change, let's say, a xpath "address" of a advancedDataGrid item and have all the corresponding cell items changed accordingly? or how do you test content in grids in a flexible way?
If only the container changes, where the cells are nested, I would create an parent folder for the container. If the container changes you have only to change the attributes of the container to find the container again. But this only works if only the container is changed and not its structure below (cells).

Regards,
Peter
Ranorex Team