for the three methods, I need some clarification.
1 name mapping
What should testers do if they are testing a application which generates all objects dynamically?
I give you an example:
**************test scripts************************************
1 powerTax_Main = Aliases["PowerTax_Main"];
2 gridControl = powerTax_Main["MainForm"]["MdiClient"]["WindowForm"]["AirlineView"]["AirlineWorkspace"]["AirlineGridWorkPage"]["AirlineGridWorkSpace"]["MetaViewer"]["rootTable"]["Content"]["ListFields"]["List"];
3 gridControl["ClickNewRowCellXY"]("Benefit Type", 49, 10);
4 gridControl["ClickNewRowCellXY"]("Benefit Type", 55, 10);
5 gridControl2 = powerTax_Main["PopupGridLookUpEditForm"]["GridControl"];
6 gridControl2["ClickCellXY"](0, "Code", 47, 8);
when I replay the testscript I recorded minutes ago, some of the objects in the test scripts are no longer exists. but some of them still remain in the memory, and my application will give the newly generated objects new name. Then how can I achieve the name mapping in test scripts?
2 Using find, findChild or findID.
findChild will be the last thing I want to do because I have to do many program to make it work, and I am not sure whether my program can really tame this method.. using findID, what if there is no ID for my custom controls?
3 Enumeration... Gosh. that' the pain in the AXX.. I have to do enumeration everytime when TC can't identify an object?what if I have more than 50 objects TC can't identify.. Do I need to do enumeration everytime? If i do that, i prefer to use manual testing because probably I could save more time....
