port automation to new software version
Hi, I'm using testcomplete to automatically test a new version of software that I've tested it's old version previously, there are many objects in the new software version that have different n...
Forum Discussion
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. :))
> 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. :))
