How to maintain scripts for ID changes??
The application for which scripts have been recorded has ID changes in every release and hence scripts maintennace is required everytime.
What is the best way to prevent/manage this??
Could be defining some sort of constants file and storing all ids there, but not sure if this is ok and how hectic would it be updating 150 scripts??
Re: How to maintain scripts for ID changes??
I don't think changing ID in every release is a good practice (at least not from testing point of view), but if there is no hope to make the dev guys change such practice, the workarounds could be 1) find another attribute of the object that is unique enough to identify this object. if this failed, then 2) use combinations of a few attributes, may be of a few different objects, to pinpoint the object in concern. This would need some dirty scripting, and collecting the objects in an application window may take up to a few dozens of seconds. But it's doable.