Auto update scripts when Name Mapping items/aliases are renamed

dbattaglia - Thanks for the response. I understand that my explaination should have been better. 

My suggestion was to Store all the objects in a external file (Excel or CSV or DB) and reference it in the script. So if any updates, then it is easier to update on external file. 

The objects, The object properties and Object identification must be stored irrespective of either it is Descriptive, NameMapping or Xpath or any other method. This is help to maintain the script which can be updated easily.

The requested feature is, Whenever there is an update or change in the Namemapping, the respective code in the script file must change. 

Option 1: If any Object property is changed eg: idStr - txtUserName to UserNametextbox, then the object properties can be updated in the namemapping, Which doesn't require to change in the script but it is udpated.Reference Object in External file

Option 2: If the NameMapping Object (UserName) "NameMapping.Browser.Page.Username" is changed to "NameMapping.Browser.Page.UsernameTextbox" in the namemapping file, So the scripts should get changed.

If this option is implemented, Feel this can be drawback in code maintaince. For eg: UserName - NameMapping is getting changed and it is been referenced at multiple places. So the Changes will impact in all the places. So to track is changes or identify the places of changes will be a difficult. 

I understand, The NameMapping is not required to change when you can update the property without changing the NameMapping reference.

To support option 1: 

Eg: Store the object in an excel. The reference to be used, So even if the Object identification is updated will impact on Excel file (To be updated). But not to change the reference in the script. 

I respect your thoughts and 64 Likes of expecting this feature. I'm sharing my thoughts of using the current feature.

Let me know, if i misunderstood the suggestion. 

Regards

Valla

https://vallatestcomplete.wordpress.com/