port automation to new software version

Hi,



This completely depends on your tested application and how your test project was implemented.

If you used coded approach to identify GUI object then you will need to update the code. If you used NameMapping, Namemapping tree must be updated correspondingly (you may consider using configurations functionality in NameMapping to make the code work with old and new versions of the tested software).

Whether such corrections can be done more or less quickly or every object must be processed individually depends on how developers made the changes. If they made changes in unified and consistent way you may use this advantage, otherwise you'll have to follow the object-per-object way.

Thanks Alex for your reply,



I'm using name mapping approach, and the objects names and parents are changed.



please can you clarify what you mean by :



"If they made changes in unified and consistent way you may use this advantage, otherwise you'll have to follow the object-per-object way."



how could i use this advatnage instead of follow the object-per-object way ?? is there a specific approach to follow ??



Thanks,

Hi,



> please can you clarify [...]



I meant that, for example, the change could be the replacement of all standard buttons on all dialogs with custom button descendant from the standard one. In this case you had to replace all 'TButton' strings with, say, 'TYourCustomButtonClass' for all dialog windows in NameMapping.

Or the change could be to introduce additional panel in the lower part of all windows that contain grid and move grid controls to this panel.

For all above examples the changes to NameMapping can be done more or less easily and in a unified way.

But if the changes were like replace combo-box on this form with the list box and move all buttons on that form two layers of panels deeper and completely redesign one more form, and... Then obviously you have no other choice than run your test suite and go error by error and check if it occurred because of user interface change and correct NameMapping (and, probably, code) so that it matches the changed UI.



Oh, and you may thank to Development and require an extra pizza from them for the fact that they did not warn you ahead about such significant changes in the UI. :))