In general the script / object should reflect the same name. If any object name has been changed in application and then definitely you need to update that object with the new name. So that you know which object the script is referring.
We don't execute test wizard for updating the object, because you are updating the a particular object not all the objects. If you update all the object in GUI then you need to update the same in script too. If you have customized the object logical name according to need then all the rework needs to be done if you update through wizard
If you want a high quality software system, you must ensure each of its parts is of high quality. by Watts S. Humphrey
Thank you for answering my questions.
Im back with another one: Why would you need to modify logical names in the map editor ? If the name of a particular object has changed would you not want to just run the test wizard again ?Why would you want to edit the Name of the object.
In this case, you can choose Event Driven Testing.
In which scripts deals with only .xls sheets. in which window name, oject name and event to be performed on that particular object can be defined.
Instead of hard coding object name in the script, we can make our script to get the logical name from .xls sheet.
When object name is changed, we can just change those names in .xls. there is no need to update logical name of the object in the scripts.
This method even helps when the navigation of the application is changed. suppose window1 > Window2> Window3 is changed to Window1 > Window3 . then change the choice in .xls as N.
When a window choice in Y in .xls then only Scripts should perform operations on that particular window.
CHOICE Window C1 D1 C2 D2 A1
Y LOGIN Uname aaa Pwd ppp OK
Y USERDATAName xxx Desig SE OK
Here, C1,C2, ..are control names.
D1, D2, ..are corresponding data for the controls
A1,..are control names on which event(click etc)is to be performed.