What stack does your tech team use?
If they are C#, then they should adhere to an automationId just for you.
But if they are adding and removing elements all the time, that probably indicates the app itself isn't even at a stable state for you to spend time automating.
They should also adhere to a design methodology that is sensible. For example lets say they have a panel (in a C# app, webapp whatever) called customerOrders. and within the customerOrders they have an inputfield called 'address'. It is sensible that if I find the customerOrder panel, then look for address, I should be getting the customer address field, even if 'address' itself is a bit ambiguous.
If dev change that, they may put a wrapper around address or whatever. But fact is from design, if I go find a customerOrder panel then look for address, I should still arrive at the same object.
Not sure if that makes any sense.
Hey!
Thanks KSQian!
We are using Delphi7 currently and going through the process of upgrading to XE at present. Shame on us, I know. Firstly using Delphi but then also upgrading to a version that is not the latest. This is where we find ourselves however.
They aren't adding & removing objects all the time as such, it's more that the hierachy of an object or two had changed. It feels a much bigger problem when it happens, probably because of the frequency of the the interaction with the objects in question. It was a pretty daunting feeling at the time, thinking I was going to have to sit there and manually fix each step!! Not good. Sorry, if that was misleading... Saying that, object recognition is a common problem for us, but this is the first time the cause has been the addition of new objects and changes in hierarchy.
As for any wrappers being implemented I'm not sure. I understand your point though and believe the object hierarchy that we have does make sense in this way, which is a help.
Thanks for your help!
